[teiid-issues] [JBoss JIRA] (TEIID-1899) Getting Assertion when running Inner Merge Join query with SELECT COUNT(*) on top

[ https://issues.jboss.org/browse/TEIID-1899?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1899. ----------------------------------- Fix Version/s: 7.6.1 8.0 Resolution: Done The issue is that distinct dependent tuple buffers are being removed (previously a new tuplebuffer was always created regardless of whether the distinct operation was needed or not). Note that this issue was also partially due to the dependent join backoff logic, since that was triggering a normal handling of the effective semi-join. 7.4.x may also benefit from change r3780 that more narrowly applies the backoff logic to only when column ndv values are known. I noticed a TODO in that we could be doing a better value of sharing potentially distinct sorted independent results with the dependent join logic. For a non-enhanced merge, currently both the dependent join and the criteria handling logic will perform a sort. -- 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