[JBoss JIRA] (TEIID-2885) Allow dependent join pushdown to be chosen by the planner
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2885?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2885:
---------------------------------------
dependentJoinPushdownThreshold has been removed for 8.11. That will give the optimizer more flexibility in utilizing full pushdown. Also the hints will be updated to prevent that if needed.
> Allow dependent join pushdown to be chosen by the planner
> ---------------------------------------------------------
>
> Key: TEIID-2885
> URL: https://issues.jboss.org/browse/TEIID-2885
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> As a follow on to TEIID-2249, the planner should be able to choose when to use full join pushdown, rather than only relying upon a hint. One downside to this currently is that there isn't a good way to do a back off to a different join processing (unless we embedded an alternative plan) and so we may have to add failure logic if too many independent values are retrieved.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3530) dependent join enhancements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3530?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3530:
---------------------------------------
Made the initial commit. This added an optional JDBC parameter to control whether dependent join values are bind values or not. It will default to false for oracle, but otherwise will be true. Although in testing it did not appear that newer versions of oracle, such as 12, had a problem with large prepared statements.
Removed the dependentJoinPushdownThreshold and instead looked at the additional processing that could be performed. If there is significant post-processing then even without a hint, we'll fully push the dependent join. We will need to expand the hint syntax to also prevent this from happening.
Also the dependent criteria processor will not use the key only temp table method for simple/small dependent joins. The tuning for that seemed fairly consistent for oracle and sql server sources.
> dependent join enhancements
> ---------------------------
>
> Key: TEIID-3530
> URL: https://issues.jboss.org/browse/TEIID-3530
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> We need to address several aspects of dependent joins:
> - allow for translators to control if bind variables will be used (oracle should not)
> - remove the dependentJoinPushdownThreshold option and allow the planner to fully push the join based upon the plan
> - have rule choose dependent make a better determination of when to use a temp table vs. in predicates.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3542) Logging does not print full queries which contain ESCAPE '\u0000' clause
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3542?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3542:
---------------------------------------
I should back off of the previous comment a little. A partial solution that would fix this specifically for the escape clause and string literals would be to update the sql string visitor logic to use the unicode escapes for control characters. But that wouldn't be a complete solution as it could still appear in a logged value or other places.
> Logging does not print full queries which contain ESCAPE '\u0000' clause
> ------------------------------------------------------------------------
>
> Key: TEIID-3542
> URL: https://issues.jboss.org/browse/TEIID-3542
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.10.1
> Environment: Possibly only happens on Linux.
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Priority: Trivial
>
> Queries submitted to Teiid containing the NUL character for the ESCAPE character are not properly printed to jboss logging.
> Seems that the NUL character can be used within java Strings but when the String is printed to the display, it terminates at the first NUL character it reaches. This result in "... ESCAPE '\u0000' ... being printed as "... ESCAPE '".
> See [here|https://gist.github.com/phantomjinx/fef25524e7e9844c4f3d] for an example of a jboss log with such a query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3542) Logging does not print full queries which contain ESCAPE '\u0000' clause
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3542?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3542.
-----------------------------------
Fix Version/s: (was: 8.7.1.6_2)
Resolution: Rejected
This should only be an issue with the editor used to look at the file - it will still contain all of the data. Also if we want to pursue a resolution, it should go against the relevant logging framework as this would be a general consideration.
> Logging does not print full queries which contain ESCAPE '\u0000' clause
> ------------------------------------------------------------------------
>
> Key: TEIID-3542
> URL: https://issues.jboss.org/browse/TEIID-3542
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.10.1
> Environment: Possibly only happens on Linux.
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Priority: Trivial
>
> Queries submitted to Teiid containing the NUL character for the ESCAPE character are not properly printed to jboss logging.
> Seems that the NUL character can be used within java Strings but when the String is printed to the display, it terminates at the first NUL character it reaches. This result in "... ESCAPE '\u0000' ... being printed as "... ESCAPE '".
> See [here|https://gist.github.com/phantomjinx/fef25524e7e9844c4f3d] for an example of a jboss log with such a query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3542) Logging does not print full queries which contain ESCAPE '\u0000' clause
by Paul Richardson (JIRA)
Paul Richardson created TEIID-3542:
--------------------------------------
Summary: Logging does not print full queries which contain ESCAPE '\u0000' clause
Key: TEIID-3542
URL: https://issues.jboss.org/browse/TEIID-3542
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.10.1
Environment: Possibly only happens on Linux.
Reporter: Paul Richardson
Assignee: Steven Hawkins
Priority: Trivial
Queries submitted to Teiid containing the NUL character for the ESCAPE character are not properly printed to jboss logging.
Seems that the NUL character can be used within java Strings but when the String is printed to the display, it terminates at the first NUL character it reaches. This result in "... ESCAPE '\u0000' ... being printed as "... ESCAPE '".
See [here|https://gist.github.com/phantomjinx/fef25524e7e9844c4f3d] for an example of a jboss log with such a query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months