[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5867:
----------------------------------
Fix Version/s: 13.1
13.0.2
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Story Points: 0.5
Sprint: DV Sprint 56
> Support capturing the IMPORT FORIGN DATA in DDLStringVisitor
> ------------------------------------------------------------
>
> Key: TEIID-5867
> URL: https://issues.redhat.com/browse/TEIID-5867
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 13.0
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1, 13.0.2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario.
> However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugi... ]
Work on TEIID-5867 started by Steven Hawkins.
---------------------------------------------
> Support capturing the IMPORT FORIGN DATA in DDLStringVisitor
> ------------------------------------------------------------
>
> Key: TEIID-5867
> URL: https://issues.redhat.com/browse/TEIID-5867
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 13.0
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
>
> In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario.
> However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-145) Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis
by Van Halbert (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-145?focusedWorklogId=12449659&pa... ]
Van Halbert logged work on TEIIDSB-145:
---------------------------------------
Author: Van Halbert
Created on: 18/Dec/19 12:55 PM
Start Date: 16/Dec/19 12:54 PM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 3 hours, 56 minutes)
Time Spent: 4 hours, 4 minutes (was: 4 minutes)
Worklog Id: (was: 12449659)
> Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis
> ----------------------------------------------------------------
>
> Key: TEIIDSB-145
> URL: https://issues.redhat.com/browse/TEIIDSB-145
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: core
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 4 hours
> Time Spent: 4 hours, 4 minutes
> Remaining Estimate: 0 minutes
>
> To match the version with Syndesis, move the Spring Boot to 2.1.6.RELEASE
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-145) Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis
by Van Halbert (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-145?focusedWorklogId=12449658&pa... ]
Van Halbert logged work on TEIIDSB-145:
---------------------------------------
Author: Van Halbert
Created on: 18/Dec/19 12:54 PM
Start Date: 16/Dec/19 12:53 PM
Worklog Time Spent: 4 minutes
Work Description: Worked thru building community and product to ensure alignment works.
Issue Time Tracking
-------------------
Remaining Estimate: 3 hours, 56 minutes (was: 4 hours)
Time Spent: 4 minutes
Worklog Id: (was: 12449658)
> Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis
> ----------------------------------------------------------------
>
> Key: TEIIDSB-145
> URL: https://issues.redhat.com/browse/TEIIDSB-145
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: core
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 4 hours
> Time Spent: 4 minutes
> Remaining Estimate: 3 hours, 56 minutes
>
> To match the version with Syndesis, move the Spring Boot to 2.1.6.RELEASE
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5869) Update core-release profile
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5869?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5869:
----------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Sprint: DV Sprint 56
> Update core-release profile
> ---------------------------
>
> Key: TEIID-5869
> URL: https://issues.redhat.com/browse/TEIID-5869
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
> Fix For: 13.1, 13.0.2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> For the 7.6 release, need to update the core-release profile so that it builds all connectors except the following:
> - infinispan (removed from 7.6 release)
> - sandbox
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5869) Update core-release profile
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5869?focusedWorklogId=12449656&pag... ]
Steven Hawkins logged work on TEIID-5869:
-----------------------------------------
Author: Steven Hawkins
Created on: 18/Dec/19 11:52 AM
Start Date: 18/Dec/19 11:52 AM
Worklog Time Spent: 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 1 hour, 30 minutes (was: 2 hours)
Time Spent: 30 minutes
Worklog Id: (was: 12449656)
> Update core-release profile
> ---------------------------
>
> Key: TEIID-5869
> URL: https://issues.redhat.com/browse/TEIID-5869
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
> Fix For: 13.1, 13.0.2
>
> Original Estimate: 2 hours
> Time Spent: 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> For the 7.6 release, need to update the core-release profile so that it builds all connectors except the following:
> - infinispan (removed from 7.6 release)
> - sandbox
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5864?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5864:
----------------------------------
Fix Version/s: (was: 12.3.1)
> Teiid Query Join Plan Infinite Loop
> -----------------------------------
>
> Key: TEIID-5864
> URL: https://issues.redhat.com/browse/TEIID-5864
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.2.2, 12.3.2
>
> Original Estimate: 4 hours
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> We are getting an infinite loop when executing the below SQL:
> {code:java}
> SELECT c._COMPTE,
> u.CalculatedField,
> cl.CHAMPSFCP__VALEUR,
> ch_41.CH41__VALEUR,
> ch_5.CH5__VALEUR
> FROM OmgModel_Z1rP.OMG.dbo.CPARTFCP c
> LEFT JOIN BInv6BusinessModel.FREPACCOUNTUNION u
> ON u.FREP_AFAINB = c._USERNAME
> AND u.CalculatedField6 = 'B'
> LEFT JOIN BInv6BusinessModel.ClientTypeCode cl
> ON c._COMPTE = cl.CHAMPSFCP__COMPTE
> LEFT JOIN (SELECT ch._COMPTE AS CH41__COMPTE,
> ch._VALEUR AS CH41__VALEUR
> FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch
> WHERE ch._NUMCHAMPS = 41) ch_41
> ON c._COMPTE = ch_41.CH41__COMPTE
> LEFT JOIN (SELECT ch._COMPTE AS CH5__COMPTE,
> ch._VALEUR AS CH5__VALEUR
> FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch
> WHERE ch._NUMCHAMPS = 5) ch_5
> ON c._COMPTE = ch_5.CH5__COMPTE LIMIT 0, 10
> {code}
> After debugging, find out that the issue is coming from the class RulePlanOuterJoins method planLeftOuterJoinAssociativityBeforePlanning.
> the issue is coming from the below code line, if removed the issue is not reproduced:
> {code:java}
> changedAny |= val;
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years