[JBoss JIRA] (TEIID-5833) Update extension metadata uri's
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5833:
---------------------------------------
One more issue is that rest vdbs use the fqn property keys on vdb properties. I've added a fix, but more than likely we'll want to move the code that checks for the legacy form to common place so that it can be used from the admin logic as well.
> Update extension metadata uri's
> -------------------------------
>
> Key: TEIID-5833
> URL: https://issues.jboss.org/browse/TEIID-5833
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes.
> The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[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 resolved TEIID-5740.
-----------------------------------
Resolution: Done
Narrowed the scope of this issue to only the explain statement. Added and documented. We will not create a prepared statement nor cache the results, but otherwise the actual command may execute unmolested.
> 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, 1 month
[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:
---------------------------------------
> Are you saying that for Fuse 7.6, teiid will be staying on its 12.3.x version or will it be releasing off 13.x?
No, I'm saying there is nothing currently referencing it.
> But I can setup the initial build to use the teiid 12.3.x branch.
Yes, then we can worry about this if/when teiid-syndesis/teiid-spring-boot need to migrate which would ideally be after teiid 13 final.
> 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, 1 month