[JBoss JIRA] (TEIID-4558) Query Plan Analyzer
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4558?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4558:
----------------------------------
Fix Version/s: 12.x
(was: 11.x)
> Query Plan Analyzer
> -------------------
>
> Key: TEIID-4558
> URL: https://issues.jboss.org/browse/TEIID-4558
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Affects Versions: 9.2
> Reporter: Van Halbert
> Priority: Major
> Fix For: 12.x
>
>
> Provide a tool that would take a query plan and provide feed back.
> Example:
> - indicate where there maybe a problem in the structure of the query that may impact performance
> - indicate in the plan where there maybe issues (like table scan, no rows, etc.)
> - provide recommendations for improving performance
> etc..
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (TEIID-4900) Implement limit to / exclude import options
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4900?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4900:
----------------------------------
Fix Version/s: 12.x
(was: 11.x)
> Implement limit to / exclude import options
> -------------------------------------------
>
> Key: TEIID-4900
> URL: https://issues.jboss.org/browse/TEIID-4900
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors, Query Engine
> Affects Versions: 9.2
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 12.x
>
>
> TEIID-4899 removed support for LIMIT TO / EXCLUDE since the semantics of LIMIT TO / EXCLUDE does not match the regex base support in several of the translators. Also JDBC does not support a specific include, only exclude.
> There are two options:
> These need to be handled at the engine level as general options instead - and leave the import settings to be importer specific. However that requires generic logic for repairing the metadata should a foreign key or other references be made to an excluded table.
> If they are mapped to translator options then we'll need to translate the table names in the an appropriate regex expression.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months