[
https://issues.jboss.org/browse/TEIID-3452?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3452:
---------------------------------------
Are you ok with just a formatting change to the annotation lines:
priority [category] annotation - resolution
Or can suggest something else?
To add more context the notion of an annotation priority is localized.
High - it's not an error, but indicative that something is likely not correct. For
example a hint that cannot be applied.
Medium - a major planning decision such as something around materialization, the use of
document streaming for xquery, etc.
Low - almost a debug level statement of why a planning decision was made.
So something like criteria not being pushed is not necessarily an issue, just a planning
decision. If the translator has no support, then that is the best that we can do.
If you are looking for a something more qualitative from a user perspective, that would be
something new.
Better highlighting in the query plan when an identified possible
issue is seen
-------------------------------------------------------------------------------
Key: TEIID-3452
URL:
https://issues.jboss.org/browse/TEIID-3452
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.11
Reporter: Van Halbert
Assignee: Steven Hawkins
Looking a query plan that's printed in the server log, I see the following line:
"LOW Relational Planner Negation is not supported by source People -
People.Person.id < 2 was not pushed"
Can the words "LOW Relational Planner Negation" be rephrased?
The word "LOW" used in the context of the criteria not being pushed down would
seem to me to be a possible CRITICAL issue to performance. And I'm not sure most
users will claim to know what Relational Planner Negation means and what its implying on
an error message.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)