May 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-169) JDG caching for multi-pod dv

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-169?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-169: --------------------------------- Fix Version/s: 1.6.0 (was: 1.5.0) > JDG caching for multi-pod dv > ---------------------------- > > Key: TEIIDSB-169 > URL: https://issues.redhat.com/browse/TEIIDSB-169 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.6.0 > > > For multi-pod support we need to: > * Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication. > * replace the logic that detect failed materialization loads -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-202) update Teiid dependency to 14.0 and release

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-202: ------------------------------------ Summary: update Teiid dependency to 14.0 and release Key: TEIIDSB-202 URL: https://issues.redhat.com/browse/TEIIDSB-202 Project: Teiid Spring Boot Issue Type: Task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Update the Teiid version and release 1.5.0 version -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5861) Salesforce translator should support nested joins

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5861?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIID-5861: -------------------------------------- Hi! How about this task? We hard need this functionality from teiid. Please, please, please :) > Salesforce translator should support nested joins > ------------------------------------------------- > > Key: TEIID-5861 > URL: https://issues.redhat.com/browse/TEIID-5861 > Project: Teiid > Issue Type: Enhancement > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > Original Estimate: 2 days > Remaining Estimate: 2 days > > For this SQL we have wrong generated SOQL > {code} > select > price.Id, > price.IsActive__c, > price.name, > price.PriceBook__c, > book.DefaultCurrency__c, > price.Price__c, > price.ProductCode__c, > price.ProductName__c, > price.Product__c, > product.Id, > product.Name, > product.Description > from > MSRP__c as price > left outer join /*+ MAKEDEP */ Product2 as product on > price.Product__c = product.id > left outer join /*+ MAKEDEP */ Pricebook2 as book on > price.PriceBook__c = book.id > where > price.PriceBook__c =:priceBookId > and ProductCode__c in( > :productCodes > ) > and IsActive__c = true" > {code} > {code} > START DATA SRC COMMAND: startTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=3 executionID=2 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sql=SELECT sf.Pricebook2.DefaultCurrency__c FROM sf.Pricebook2 WHERE sf.Pricebook2.Id = 'xxxxx' > [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker0_QueryProcessorQueue1]: SOURCE SRC COMMAND: endTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=2 executionID=1 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sourceCommand=[SELECT MSRP__c.Id, MSRP__c.IsActive__c, MSRP__c.Name, MSRP__c.PriceBook__c, MSRP__c.Price__c, MSRP__c.ProductCode__c, MSRP__c.ProductName__c, MSRP__c.Product__c, Product__r.Id, Product__r.Name, Product__r.Description FROM MSRP__c WHERE (MSRP__c.PriceBook__c = 'xxxx') AND ((MSRP__c.ProductCode__c IN(xxxxx)) AND (MSRP__c.IsActive__c = true))] > [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.CONNECTOR [Worker1_QueryProcessorQueue2]: salesforce.9MPiB/GOwB5f.9MPiB/GOwB5f.0.3: Incoming Query: SELECT Pricebook2.DefaultCurrency__c FROM Pricebook2 WHERE Pricebook2.Id = 'xxxx' > [2019-12-02 12:43:54,368 MSK] DEBUG [salesforce-failover-facade,,,] org.teiid.COMMAND_LOG.SOURCE [Worker1_QueryProcessorQueue2]: SOURCE SRC COMMAND: endTime=2019-12-02 12:43:54.368 requestID=9MPiB/GOwB5f.0 sourceCommandID=3 executionID=2 txID=null modelName=sf translatorName=salesforce sessionID=9MPiB/GOwB5f principal=anonymous sourceCommand=[Using retrieve: Pricebook2.DefaultCurrency__c Pricebook2 [xxxx]] > {code} > But need to generate one. Because we have two relations in MSRP__c -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5956) remove xml dependencies

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5956?focusedWorklogId=12451125&pag... ] Steven Hawkins logged work on TEIID-5956: ----------------------------------------- Author: Steven Hawkins Created on: 20/May/20 10:20 PM Start Date: 20/May/20 10:20 PM Worklog Time Spent: 1 hour Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 30 minutes) Time Spent: 1 hour Worklog Id: (was: 12451125) > remove xml dependencies > ----------------------- > > Key: TEIID-5956 > URL: https://issues.redhat.com/browse/TEIID-5956 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.1 > > Original Estimate: 30 minutes > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > xom drags in xml-apis, xerces, and xalan as dependencies - but none of stream processing tests seem to need to pass. These should all be excluded. This will also help with syndesis alignment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5956) remove xml dependencies

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5956?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5956. ----------------------------------- Resolution: Done excluded or removed dependencies on xml-apis, xalan, and xerces. > remove xml dependencies > ----------------------- > > Key: TEIID-5956 > URL: https://issues.redhat.com/browse/TEIID-5956 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > xom drags in xml-apis, xerces, and xalan as dependencies - but none of stream processing tests seem to need to pass. These should all be excluded. This will also help with syndesis alignment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5957) enable EXTRACT DOW from timestamp

by Ken Geis (Jira)

Ken Geis created TEIID-5957: ------------------------------- Summary: enable EXTRACT DOW from timestamp Key: TEIID-5957 URL: https://issues.redhat.com/browse/TEIID-5957 Project: Teiid Issue Type: Enhancement Components: Grammar Affects Versions: 13.1 Reporter: Ken Geis Assignee: Steven Hawkins Similar to TEIID-5896, I would like Teiid to support {code:sql} EXTRACT(DOW FROM ...) {code} for Tableau compatibility. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5956) remove xml dependencies

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5956: ------------------------------------- Summary: remove xml dependencies Key: TEIID-5956 URL: https://issues.redhat.com/browse/TEIID-5956 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 14.1 xom drags in xml-apis, xerces, and xalan as dependencies - but none of stream processing tests seem to need to pass. These should all be excluded. This will also help with syndesis alignment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5943: ------------------------------------- I need to check this again, as when I was doing the demo, I saw an issue accessing the status table, did not yet debug it, maybe something completely separate from this. > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1, 8.0-tp1-13.1.x > > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5930) FULL JOIN missing data when not using LIMIT clause

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5930?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5930: ---------------------------------- Sprint: DV Sprint 62 > FULL JOIN missing data when not using LIMIT clause > -------------------------------------------------- > > Key: TEIID-5930 > URL: https://issues.redhat.com/browse/TEIID-5930 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 13.1 > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 14.0, 13.0.3, 13.1.1 > > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 1 hour > > When commenting out/uncommenting limit clause in the query: > {code:sql} > SELECT COUNT(*) > FROM > ( > SELECT > date_value1 > , id > FROM views.view1_m > Limit 1000000000 > ) v1 > full > JOIN > ( > SELECT > date_value2 > , id > FROM views.view2_m > LIMIT 1000000000 > ) v2 > ON > v1.date_value1 = v2.date_value2 > and v1.id = v2.id ;; > {code} > teiid returns different results, for example, when using limits in all subqueries Teiid will return 3652, but when commenting out all limit clauses teiid in turn will return already 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5943: ---------------------------------- Sprint: DV Sprint 63 > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1, 8.0-tp1-13.1.x > > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2020