[JBoss JIRA] (TEIID-5876) MongoDB import name conflict issues
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5876?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5876:
----------------------------------
Fix Version/s: 14.0
(was: 13.x)
> MongoDB import name conflict issues
> -----------------------------------
>
> Key: TEIID-5876
> URL: https://issues.redhat.com/browse/TEIID-5876
> Project: Teiid
> Issue Type: Bug
> Components: …
[View More]Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> There are two issues with the import logic and naming:
> 1. There's an assumption that any table in the schema was created by the mongodb import. In general this is not true as other imports or ddl may have already run.
> 2. If a child construct has a field name that matches an existing table, the two entities will get intertwined in the metadata, which is invalid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
5 years
[JBoss JIRA] (TEIID-5876) MongoDB import name conflict issues
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5876?page=com.atlassian.jira.plugi... ]
Work on TEIID-5876 started by Steven Hawkins.
---------------------------------------------
> MongoDB import name conflict issues
> -----------------------------------
>
> Key: TEIID-5876
> URL: https://issues.redhat.com/browse/TEIID-5876
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: …
[View More]Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> There are two issues with the import logic and naming:
> 1. There's an assumption that any table in the schema was created by the mongodb import. In general this is not true as other imports or ddl may have already run.
> 2. If a child construct has a field name that matches an existing table, the two entities will get intertwined in the metadata, which is invalid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
5 years
[JBoss JIRA] (TEIID-226) Cacheing translated commands would improve connector performance
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-226?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-226.
----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Won't Do
> Cacheing translated commands would improve connector performance
> ----------------------------------------------------------------
>
> Key: TEIID-226
> URL: https://issues.redhat.com/browse/TEIID-226
> Project: Teiid
…
[View More]> Issue Type: Feature Request
> Components: Connector API, Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Priority: Major
>
> Defect Tracker #16722: AD 2/17/05 - Command translation in connector - approx. half the time taken to create an Execution object is spent in command translation. If there was a way to cache the translated command, then we could eliminate that step for subsequent requests.
> Alex 2/17/05 - The problem is that the connector can be used with different vdbs, so the translation may be different even for the same query. Still seems do-able [...].
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
5 years