[JBoss JIRA] Created: (TEIID-1166) Receiving ASSERTION FAILED: expected reference to be not null from SQL query with sub-select
by Paul Nittel (JIRA)
Receiving ASSERTION FAILED: expected reference to be not null from SQL query with sub-select
--------------------------------------------------------------------------------------------
Key: TEIID-1166
URL: https://jira.jboss.org/browse/TEIID-1166
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Environment: Fedora 12, Teiid 7 Final
Reporter: Paul Nittel
Assignee: Steve Hawkins
Attachments: RecursiveText_MPS.zip, serverLogSnippetEmployees.txt
Using a model built in Designer, and a text file-based data source, I queried SELECT * FROM "EmployeeData"."Employee" WHERE annualSalary < (SELECT AVG(annualSalary) FROM "EmployeeData"."Employee") using SQuirreL and received this exception:
2010-07-23 13:33:48,169 DEBUG [org.teiid.PROCESSOR] (WorkManager(2)-44_QueryProcessorQueue141) [Ljava.lang.Object;@913388
java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
at org.teiid.core.util.Assertion.failed(Assertion.java:76)
at org.teiid.core.util.Assertion.isNotNull(Assertion.java:307)
at org.teiid.core.util.Assertion.isNotNull(Assertion.java:299)
at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:347)
at org.teiid.query.processor.relational.TextTableNode.initialize(TextTableNode.java:115)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:74)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:79)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:79)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:79)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:79)
at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:69)
at org.teiid.query.processor.QueryProcessor.<init>(QueryProcessor.java:86)
at org.teiid.dqp.internal.process.Request.createProcessor(Request.java:356)
at org.teiid.dqp.internal.process.Request.processRequest(Request.java:452)
at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:346)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:167)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49)
at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190)
at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187)
at org.teiid.dqp.internal.process.StatsCapturingWorkManager$WorkWrapper.run(StatsCapturingWorkManager.java:102)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Each part of the query works independently. I will attach more of the log file and the Model Project Set.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (TEIID-1182) UDF model is not being loaded if the file is not placed in the root location of VDB
by Ramesh Reddy (JIRA)
UDF model is not being loaded if the file is not placed in the root location of VDB
-----------------------------------------------------------------------------------
Key: TEIID-1182
URL: https://jira.jboss.org/browse/TEIID-1182
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Critical
Fix For: 7.1
When the "UDF" model is placed in sub-directory other than the root directory, the VDB deployer is unable to the UDF model. The reason is VDB deployment scanner only scans the VDB artifact in known locations of the VDB directory structure. All other locations are ignored.
The possible solutions are
1) Place the UDF always in root location of VDB
2) Place the UDF file in a known sub-directory like "UDF"
3) Make the VDB deployer scan all the directories.
Although (3) seems to be most flexible option, I am not sure that is possible. In that case (2) needs to be pursued, along with tooling support.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months