[JBoss JIRA] (TEIID-5740) Add support for EXPLAIN
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5740:
---------------------------------------
There really isn't an immediate visual aspect. This is the same plan form you can get over JDBC (either via the old jdbc extension, or with with SET SHOWPLAN etc.). The difference is for pg clients. It's superficially the same syntax as pg and the implementation details of the other methods (only available over jdbc or dependent on the last executed statement, which due to metadata queries may not be the user query) you couldn't really get the query plan from the client.
> Add support for EXPLAIN
> -----------------------
>
> Key: TEIID-5740
> URL: https://issues.jboss.org/browse/TEIID-5740
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> We need another mechanism for viewing plans - either a procedure or a table. We also have a lot of vdb information that is not exposed via system metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5740) Add support for EXPLAIN
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-5740 at 10/31/19 5:46 PM:
---------------------------------------------------------------
cool (y), we need to think some visual aspect to it
was (Author: rareddy):
cool (y)
> Add support for EXPLAIN
> -----------------------
>
> Key: TEIID-5740
> URL: https://issues.jboss.org/browse/TEIID-5740
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> We need another mechanism for viewing plans - either a procedure or a table. We also have a lot of vdb information that is not exposed via system metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5835?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5835:
---------------------------------------
Staying at 4.6 means that ~3 odata issues remain unaddressed and the aggregate stuff will need modified as it's compile dependent upon changes.
Adding our own patch is a possibility, but that means backporting the fixes to 4.6 and creating an overlay project/jar.
A month is fine from a final release timeline.
> Upgrade Apache Olingo to a final version of 4.7
> -----------------------------------------------
>
> Key: TEIID-5835
> URL: https://issues.jboss.org/browse/TEIID-5835
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 13.0
>
>
> Teiid needs to upgrade from the olingo 4.7 SNAPSHOT.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5836) Add missing vdb information to system tables
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5836:
-------------------------------------
Summary: Add missing vdb information to system tables
Key: TEIID-5836
URL: https://issues.jboss.org/browse/TEIID-5836
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Separating this from TEIID-5740. We're missing vdb properties, domain types, grants, and even information about translators.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months