[teiid-issues] [JBoss JIRA] (TEIID-2040) Failed Assertion during org.teiid.query.processor.relational.SortUtility.<init>

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Wed May 16 17:15:19 EDT 2012


     [ https://issues.jboss.org/browse/TEIID-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-2040:
----------------------------------

           Description: The issue here is with push aggregates running after choose dependent and altering the schema of the independent side of a join that is later referenced by the dependent sort logic.
    Steps to Reproduce: 
SimpleRecursion.vdb attached in SFDC ticket. Can replicate by deploying VDB to server, and running the query against the VDB. 


  was:
SimpleRecursion.vdb attached in SFDC ticket. Can replicate by deploying VDB to server, and running the query [1] against the VDB. Related -ds.xml will be attached here.

[1]
SELECT E0.ID AS C0,
	R.ID AS C1 
FROM SourceCM.DEPENDANTS AS R 
LEFT JOIN (SourceCM.PARENT_CHILD AS E0 
		JOIN SourceCM.TOP AS E1 
		ON E0.PARENT_ID=E1.ID) 
ON R.PARENT_ID=E0.ID
WHERE E1.NAME='Tree 1' 
GROUP BY E0.ID,R.ID ORDER BY C1 LIMIT 0,5000

The PARENT_CHILD table is derived by a simple virtual procedure, if he switches this to a table there are no issues, so it's seem to be something with the input parameter and the procedure. Testing with his query if you just remove the WHERE clause it succeeds.  If you add the E1.NAME to the SELECT list, you'll see that there are values for this column.


    
> Failed Assertion during org.teiid.query.processor.relational.SortUtility.<init>
> -------------------------------------------------------------------------------
>
>                 Key: TEIID-2040
>                 URL: https://issues.jboss.org/browse/TEIID-2040
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.7
>            Reporter: Johnathon Lee
>            Assignee: Steven Hawkins
>             Fix For: 7.7.1, 8.1
>
>
> The issue here is with push aggregates running after choose dependent and altering the schema of the independent side of a join that is later referenced by the dependent sort logic.

--
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

        


More information about the teiid-issues mailing list