[
https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-2381:
--------------------------------------
Thanks for the examples. Much clearer to me now.
Do we accumulate source hints, or does the top level one take
precedence?
We have cases where the upper-most hint takes precedence and another case where the lowest
hint takes precendence. Any non-arbitrary solution is going to require some policy for
picking the right one(s). Ultimately, that policy needs to be encoded in the translator
or some new API. I don't see any advantage of it being a separate API. Thus, I like
the accumulate approach.
My first cut at the accumulation algorithm would be something like: (1) from the
pre-optimized structure, accumulate all hints grouped by source. For each source in the
optimized structure, send the translator the appropriate group from #1. If the translator
needs additional information and/or mapping, it's up to the programmer to encode that
information into the hint.
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