[teiid-issues] [JBoss JIRA] (TEIID-2085) Additional feature to TEIID-1726
[
https://issues.jboss.org/browse/TEIID-2085?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2085.
-----------------------------------
Resolution: Done
After further code investigations, went forward with the second option as it is fairly
well contained in the code. The general and source specific hints can now specify KEEP
ALIASES to retain the user/view aliases.
Any scenario that is not viable with this approach should be addressed by either
determining the needed aliases from the query plan or by directly issuing the query via
the native query procedure feature.
Additional feature to TEIID-1726
--------------------------------
Key: TEIID-2085
URL: https://issues.jboss.org/browse/TEIID-2085
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 8.2
Specifying the aliases in the hints added in https://issues.jboss.org/browse/TEIID-1726
do not work with even the full table name (fdm.wh_gl_daily_balances_f). However, if you
were to specify g_0 and g_1 as the aliases for the tables, the hints take effect. The
teiid engine has rewritten the query with its own internal aliases and the only way to
find out what has been specified is to actually look at the source system sql send to
Oracle.
Can we specify the table aliases of the main query in the source
hints rather than looking at what Teiid engine has rewritten to? It
is quite confusing for developers to use the source hints feature
and if the developer does not have access to the Oracle database
they wont be able to tell what has been used in the source query to
reflect the aliases in the source hints.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira