[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIID-5835?page=com.atlassian.jira.plugi... ]
Ramesh Reddy edited comment on TEIID-5835 at 12/6/19 9:46 PM:
--------------------------------------------------------------
When I updated to 4.7 snapshot I did upgrade, I did not see fail. I ran local build too before commiting not sure where it is falling
Maybe I did the update in Teiid Spring Boot not in Teiid. :(
was (Author: rareddy):
When I updated to 4.7 snapshot I did upgrade, I did not see fail. I ran local build too before commiting not sure where it is falling
> Upgrade Apache Olingo to a final version of 4.7
> -----------------------------------------------
>
> Key: TEIID-5835
> URL: https://issues.redhat.com/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
>
> Original Estimate: 1 hour
> Remaining Estimate: 0 minutes
>
> Teiid needs to upgrade from the olingo 4.7 SNAPSHOT.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5835?page=com.atlassian.jira.plugi... ]
Steven Hawkins edited comment on TEIID-5835 at 12/6/19 9:26 PM:
----------------------------------------------------------------
We'll need to do a little cleanup of the jackson dependencies. Olingo uses 2.10.0, but Teiid is using 2.9.10 ish. We can either downgrade olingo to 2.9.10 or upgrade everyone to 2.10.1. The dependency checks fail for local builds only as they have been disabled in travis.
was (Author: shawkins):
We'll need to do a little cleanup of the jackson dependencies. Olingo uses 2.10.0, but Teiid is using 2.9.10 ish. We can either downgrade olingo or upgrade everyone to 2.10.1. The dependency checks fail for local builds only as they have been disabled in travis.
> Upgrade Apache Olingo to a final version of 4.7
> -----------------------------------------------
>
> Key: TEIID-5835
> URL: https://issues.redhat.com/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
>
> Original Estimate: 1 hour
> Remaining Estimate: 0 minutes
>
> Teiid needs to upgrade from the olingo 4.7 SNAPSHOT.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-147:
--------------------------------------
sure, lets get the functionality first, then hopefully the by then we will figure out the certificate-based auth
> Caching and materialization changes for JDG / OpenShift
> -------------------------------------------------------
>
> Key: TEIIDSB-147
> URL: https://issues.redhat.com/browse/TEIIDSB-147
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Components: core, OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.3.0
>
>
> Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well.
> Things break down roughly into:
> * Single-pod support
> ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now?
> ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436
> * Multi-pod support
> ** everything from single-pod support
> ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
> ** requires replacing the logic that detect failed materialization loads
> ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5835?page=com.atlassian.jira.plugi... ]
Steven Hawkins reopened TEIID-5835:
-----------------------------------
We'll need to do a little cleanup of the jackson dependencies. Olingo uses 2.10.0, but Teiid is using 2.9.10 ish. We can either downgrade olingo or upgrade everyone to 2.10.1. The dependency checks fail for local builds only as they have been disabled in travis.
> Upgrade Apache Olingo to a final version of 4.7
> -----------------------------------------------
>
> Key: TEIID-5835
> URL: https://issues.redhat.com/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
>
> Original Estimate: 1 hour
> Remaining Estimate: 0 minutes
>
> Teiid needs to upgrade from the olingo 4.7 SNAPSHOT.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[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 commented on TEIID-5864:
---------------------------------------
This takes a certain structure containing 3 left outer joins, such that the logic things there's still something to be gained by reorganizing the joins, but really it's just shuffling the same three. It will take a little more logic to detect this terminal condition.
> 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.1
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 3 hours
>
> 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)
6 years, 4 months
[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 commented on TEIID-5864:
---------------------------------------
Thanks, that clearly reproduces it.
> 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.1
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 3 hours
>
> 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)
6 years, 4 months
[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5864?focusedWorklogId=12448306&pag... ]
Steven Hawkins logged work on TEIID-5864:
-----------------------------------------
Author: Steven Hawkins
Created on: 06/Dec/19 8:45 AM
Start Date: 06/Dec/19 8:45 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 3 hours (was: 4 hours)
Time Spent: 1 hour
Worklog Id: (was: 12448306)
> 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.1
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 3 hours
>
> 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)
6 years, 4 months
[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: 13.0
12.2.2
12.3.1
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Story Points: 1
Sprint: DV Sprint 56
> 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.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> 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)
6 years, 4 months
[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... ]
Work on TEIID-5864 started by Steven Hawkins.
---------------------------------------------
> 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
>
> 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)
6 years, 4 months