[JBoss JIRA] (TEIID-2046) StaxSource is not supported for validation, VDB deployment fails
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2046:
-----------------------------------
Summary: StaxSource is not supported for validation, VDB deployment fails
Key: TEIID-2046
URL: https://issues.jboss.org/browse/TEIID-2046
Project: Teiid
Issue Type: Bug
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
"apache.xerces" is used by default in the AS7 as the chosen jaxp library, and it does not support StaxSource as the Validator input. Consider using some other type of source like StreamSource.
Caused by: java.lang.IllegalArgumentException: Source parameter of type 'javax.xml.transform.stax.StAXSource' is not accepted by this validator.
at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:119)
at javax.xml.validation.Validator.validate(Validator.java:127) [rt.jar:1.6.0_26]
at org.teiid.adminapi.impl.VDBMetadataParser.validate(VDBMetadataParser.java:94)
at org.teiid.jboss.VDBParserDeployer.parseVDBXML(VDBParserDeployer.java:111)
at org.teiid.jboss.VDBParserDeployer.scanVDB(VDBParserDeployer.java:88)
at org.teiid.jboss.VDBParserDeployer.scanVDB(VDBParserDeployer.java:83)
at org.teiid.jboss.VDBParserDeployer.deploy(VDBParserDeployer.java:72)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TEIID-2058) Optimization places WHERE clause incorrectly when criteria not supplied for tables with joins
by Johnathon Lee (JIRA)
Johnathon Lee created TEIID-2058:
------------------------------------
Summary: Optimization places WHERE clause incorrectly when criteria not supplied for tables with joins
Key: TEIID-2058
URL: https://issues.jboss.org/browse/TEIID-2058
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Johnathon Lee
Assignee: Steven Hawkins
Reproducible behavior with the following simplified query [1]
Avoiding the error by including non-restricting criteria on tables not represented in the WHERE EXISTS clause [2].
ie: there seems to be a problem in the Optimization that writing the query similar to [2] will avoid.
[1]
SELECT
'X' as CMR_BPR_ID2
FROM
Y93
INNER JOIN
AG5
ON
1 = 1
LEFT OUTER JOIN
MFSMFL.I58 as I58
ON
1 = 1
WHERE EXISTS
(SELECT 'Y' FROM BH0 WHERE AG5.CONSENT_CLIENT_ID = 1 AND
Y93.CMR_BPR_ID2 = 1 )
[2]
SELECT
'X' as CMR_BPR_ID2
FROM
Y93
INNER JOIN
AG5
ON
1 = 1
LEFT OUTER JOIN
MFSMFL.I58 as I58
ON
1 = 1
WHERE EXISTS
(SELECT 'Y' FROM BH0 WHERE AG5.CONSENT_CLIENT_ID = 1 AND
Y93.CMR_BPR_ID2 = 1 AND
I58.FUND_CODE like '%')
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TEIID-2049) NPE during select call on a materialized table
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2049:
-----------------------------------
Summary: NPE during select call on a materialized table
Key: TEIID-2049
URL: https://issues.jboss.org/browse/TEIID-2049
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
This is a regression because of the TEIID-1981.
{code}
17:44:22,307 ERROR [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue19) TEIID30019 Unexpected exception for request qruejSyXY+pR.0: java.lang.NullPointerException
at org.teiid.query.optimizer.relational.RelationalPlanner.resolveVirtualGroup(RelationalPlanner.java:1233) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.buildTree(RelationalPlanner.java:836) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:737) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:696) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.generatePlan(RelationalPlanner.java:490) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:180) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:188) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:429) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.Request.processRequest(Request.java:449) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:534) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:278) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:217) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:241) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) [teiid-engine-8.0.0.Final.jar:8.0.0.Final]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [rt.jar:1.6.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [rt.jar:1.6.0_05]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_05]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TEIID-2051) Translator Overrides panel appears to have 2 properties mixed up
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2051?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2051.
---------------------------------
> Translator Overrides panel appears to have 2 properties mixed up
> ----------------------------------------------------------------
>
> Key: TEIID-2051
> URL: https://issues.jboss.org/browse/TEIID-2051
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 7.7
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 7.7.1, 8.1
>
> Attachments: Screen Shot 2012-05-16 at 9.38.05 AM.png
>
>
> I've attached a screen shot that includes the Translator Overrides panel from Designer and a section of the code from the implemented ExecutionFactory that's setting MaxInCriteriaSize and MaxDependentInPredicates.
> And looking at the overrides panel, it appears there's a couple of issues (correct me if I'm wrong):
> - the values for "Max number of IN predicate entries and Max number of dependent values ....." are swapped
> - the title for "Max number of dependent values across all IN predicates", appears to be incorrect as to how its applied? Isn't that value applied for each IN predicate? So if "Max number of IN predicates" is 2, and "Max number of dependent values..." is 1000, then a 1000 for each IN predicate (or a total of 2000 max) will be allowed. Is that correct?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months