[
https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2381:
---------------------------------------
Vineela, it would help more to describe your scenarios based upon bullets that I have
outlined above.
What you are getting at I believe is the last bullet - that is you want to expand upon the
usage of the hint in view layers (which is currently documented as limited to simple query
scenarios only). In this case, what do you propose to do when a source hint appears a
multiple levels of the query (concat hints, top overrides, etc.) How does the optimization
process affect the interpretation of a source hint in a view or multiple locations in a
user query - for example when placed within a subquery that is optimized to a join or a
flattened view layer?
Do you have any thoughts as to the other bullets:
Do you need something akin to global syntax support to specify where a source hint is
applicable?
Do you need the hint to appear in alternative locations in the source sql?
Expanded source hint support
----------------------------
Key: TEIID-2381
URL:
https://issues.jboss.org/browse/TEIID-2381
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Attachments: HintsExecutionFactory.java, RandomExecutionFactory.java,
RandomNumberStoredProcedureExecution.java, SysviewHintsExecutionTest.java
We currently look at the source hint in only the root user query (not in subqueries nor
the with clause) and only consider it in a very narrow set of circumstances when it's
used in a view.
--
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