[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop
by Mark Tawk (Jira)
[ https://issues.redhat.com/browse/TEIID-5864?page=com.atlassian.jira.plugi... ]
Mark Tawk commented on TEIID-5864:
----------------------------------
version 10.2.1, but the issue was reproduced after integrating the fix for TEIID-5721
> Teiid Query Join Plan Infinite Loop
> -----------------------------------
>
> Key: TEIID-5864
> URL: https://issues.redhat.com/browse/TEIID-5864
> Project: Teiid
> Issue Type: Bug
> 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)
5 years, 1 month
[JBoss JIRA] (TEIID-5862) TEIID-5314 does not account for env key name restrictions
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5862?page=com.atlassian.jira.plugi... ]
Work on TEIID-5862 started by Steven Hawkins.
---------------------------------------------
> TEIID-5314 does not account for env key name restrictions
> ----------------------------------------------------------
>
> Key: TEIID-5862
> URL: https://issues.redhat.com/browse/TEIID-5862
> Project: Teiid
> Issue Type: Quality Risk
> Components: Common
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The logic introduced in TEIID-5314 assumes that env variables can be referenced with existing teiid keys. This was supposed to work with thorntail, but I think that it would have needed to either preprocess the env and populate additional system properties, or otherwise manipulate the env keys. In any event the logic is not sound in general.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[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:
---------------------------------------
What version?
> Teiid Query Join Plan Infinite Loop
> -----------------------------------
>
> Key: TEIID-5864
> URL: https://issues.redhat.com/browse/TEIID-5864
> Project: Teiid
> Issue Type: Bug
> 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)
5 years, 1 month
[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop
by Mark Tawk (Jira)
Mark Tawk created TEIID-5864:
--------------------------------
Summary: Teiid Query Join Plan Infinite Loop
Key: TEIID-5864
URL: https://issues.redhat.com/browse/TEIID-5864
Project: Teiid
Issue Type: Bug
Reporter: Mark Tawk
Assignee: Steven Hawkins
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, 1 month
[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-147?page=com.atlassian.jira.plugi... ]
Ramesh Reddy commented on TEIIDSB-147:
--------------------------------------
I will check if there is PG library in GO, that would be best IMO, if not let's see if we can open up some custom api over actuator?
> Caching and materialization changes for JDG / OpenShift
> -------------------------------------------------------
>
> Key: TEIIDSB-147
> URL: https://issues.jboss.org/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)
5 years, 1 month