[
https://issues.jboss.org/browse/TEIID-1990?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1990:
--------------------------------------
I think I found the problem: The inf1code column is an integer data type while other
columns in the same position are type long.
Curious: If the execution factory declared that the data source supported CAST, would
Teiid have rewritten the select to include CAST(inf1code AS integer)?
UNION pushdown
--------------
Key: TEIID-1990
URL:
https://issues.jboss.org/browse/TEIID-1990
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Mark Addleman
Assignee: Steven Hawkins
Attachments: plan.txt, plan.txt
I have SQL of the form
SELECT a FROM (
SELECT a FROM ds.t1 UNION
SELECT a FROM ds.t2
) t
The execution factory extends JDBCExecutionFactory and supports everything except row
offset. It appears that the two unioned SELECTs are being executed as separate statements
rather than the entire unioned set being pushed down to the datasource.
Attached is plan
--
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