[JBoss JIRA] (TEIID-5876) MongoDB import name conflict issues
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIID-5876?page=com.atlassian.jira.plugi... ]
Ramesh Reddy commented on TEIID-5876:
-------------------------------------
[~shawkins] I do not remember the couchbase one, yes, I think we should.
> 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
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> 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... ]
Steven Hawkins resolved TEIID-5876.
-----------------------------------
Resolution: Done
This ended up being fairly easy to address as the existing test metadata highlighted the issue. Also decided to maintain backwards compatibility, but simply require users to turn on duplicate renaming.
[~rareddy] I believe in other places (couchbase?) we took the approach of generating long names for nested structures in the translator, would you have rather add an option for that?
> 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
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> 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?focusedWorklogId=12450513&pag... ]
Steven Hawkins logged work on TEIID-5876:
-----------------------------------------
Author: Steven Hawkins
Created on: 13/Mar/20 10:25 AM
Start Date: 13/Mar/20 10:25 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 2 hours (was: 4 hours)
Time Spent: 2 hours
Worklog Id: (was: 12450513)
> 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
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> 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... ]
Steven Hawkins updated TEIID-5876:
----------------------------------
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Story Points: 0.5 (was: 1)
Sprint: DV Sprint 60
> 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
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> 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-3928) Usage with analytical platforms
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-3928?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-3928.
-----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Out of Date
There are a couple of more specific issues for this work.
> Usage with analytical platforms
> -------------------------------
>
> Key: TEIID-3928
> URL: https://issues.redhat.com/browse/TEIID-3928
> Project: Teiid
> Issue Type: Sub-task
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Priority: Major
>
> We should promote analytical platforms, such as Spark/Hive/PrestoDB, with usages of Teiid/DV as a data loader (we support a wider variety of sources can have views that perform incoming transformation/filtering logic) and for top level integration (since we provide more robust client support, transaction support, and broader federation). This effort will include documentation, additional integration code, and sample code.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (TEIID-2052) Add Problem/Resolution to query problem using the query plan
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-2052?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-2052.
-----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Out of Date
The docs have been updated as to reading query plans. There are also a lot of annotations on the debug log that state things like predicate blank can't be pushed. As for a resolution though that is a little more difficult as generally if there is a compensation that can be taken we'll do so automatically. Otherwise the only option is for the user to modify their sql, typically to use different predicates.
> Add Problem/Resolution to query problem using the query plan
> ------------------------------------------------------------
>
> Key: TEIID-2052
> URL: https://issues.redhat.com/browse/TEIID-2052
> Project: Teiid
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 7.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Optional
> Attachments: INClauseNotPushedDown.odt
>
>
> Adding content that could be used for query problem resolution. The initial attachment does the following:
> - states the query problem (i.e., not pushing down the "IN" clause)
> - provides the query plan (and debug log) for the query being submitted
> - provides recommendations for resolving the problem
> - then indicates how this problem was resolved and what the resulting query plan / debug log
> The idea here is to continue to add other problem scenarios so that this information is really useful for resolving issues.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (TEIID-3280) Embedded Teiid | VDB scoped translators
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-3280?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-3280.
-----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Won't Fix
Given that our bootable runtime support has moved to a single vdb paradigm, this will likely never get worked.
> Embedded Teiid | VDB scoped translators
> -----------------------------------------
>
> Key: TEIID-3280
> URL: https://issues.redhat.com/browse/TEIID-3280
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Shiveeta Mattoo
> Assignee: Steven Hawkins
> Priority: Minor
>
> - Translator instances, once created are applicable for all VDB deployment invocations.
> - Seeking support for VDB scoped translators which could enable configuring properties for translators specific to VDB instances.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years