[JBoss JIRA] (TEIID-5526) Missing data source thorntail
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5526?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5526.
-----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Won't Fix
> Missing data source thorntail
> -----------------------------
>
> Key: TEIID-5526
> URL: https://issues.redhat.com/browse/TEIID-5526
> Project: Teiid
> Issue Type: Quality Risk
> Components: thorntail
> Reporter: Steven Hawkins
> Priority: Minor
>
> If you define a vdb and there is a source for which a jndi name is not matched with a data source from the configuration, the vdb will still be deployed, but won't be active - and there is no indication in the default console log as to the progress or lack thereof with the metadata load.
> Given the presumed static nature of thorntail deployments, this scenario should result in a failed deployment like embedded.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (TEIIDSB-177) Build time validation when the metadata is fully specified.
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-177?page=com.atlassian.jira.plug... ]
Steven Hawkins moved TEIID-5393 to TEIIDSB-177:
-----------------------------------------------
Project: Teiid Spring Boot (was: Teiid)
Key: TEIIDSB-177 (was: TEIID-5393)
Component/s: core
(was: Build/Kits)
Fix Version/s: (was: 13.x)
> Build time validation when the metadata is fully specified.
> -----------------------------------------------------------
>
> Key: TEIIDSB-177
> URL: https://issues.redhat.com/browse/TEIIDSB-177
> Project: Teiid Spring Boot
> Issue Type: Feature Request
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
>
> To tighten the development loop for creating thorntail deployments there should be a build time validation of a vdb - either just parsing, or effectively a local loading when the metadata if fully specified. That will catch any issues before generating / running the image.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 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... ]
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: 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)
6 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: 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)
6 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
> 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)
6 years