June 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5976) virtual function with same name as source function is always ambiguous

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5976?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5976. ----------------------------------- Resolution: Done Set the schema on the generated function method so that it's fully qualified name includes the schema. > virtual function with same name as source function is always ambiguous > ---------------------------------------------------------------------- > > Key: TEIID-5976 > URL: https://issues.redhat.com/browse/TEIID-5976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > If we have both a virtual schema and a source schema function with the same name, f1, then issuing a query like: > select v.f1()... > will always report that v.f1 is ambiguous because in the resolving of the function the logic at one point disregards the schema. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5977) There should be a way to push down a virtual function defined in ddl

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5977: ------------------------------------- Summary: There should be a way to push down a virtual function defined in ddl Key: TEIID-5977 URL: https://issues.redhat.com/browse/TEIID-5977 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 15.0 If you create a function that is defined in ddl, it currently requires that a translator be extended to add a pushdown function and handling. It would be better if there were a way to do this entirely in ddl. This could be either/or: 1. when the function is defined by an expression rather than a more complex procedure statement, we should check to see if that can be inlined. 2. provide a way to match source functions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5976) virtual function with same name as source function is always ambiguous

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5976?page=com.atlassian.jira.plugi... ] Work on TEIID-5976 started by Steven Hawkins. --------------------------------------------- > virtual function with same name as source function is always ambiguous > ---------------------------------------------------------------------- > > Key: TEIID-5976 > URL: https://issues.redhat.com/browse/TEIID-5976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > If we have both a virtual schema and a source schema function with the same name, f1, then issuing a query like: > select v.f1()... > will always report that v.f1 is ambiguous because in the resolving of the function the logic at one point disregards the schema. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5976) virtual function with same name as source function is always ambiguous

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5976?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5976: ---------------------------------- Description: If we have both a virtual schema and a source schema function with the same name, f1, then issuing a query like: select v.f1()... will always report that v.f1 is ambiguous because in the resolving of the function the logic at one point disregards the schema. Original Estimate: 3 hours Remaining Estimate: 3 hours > virtual function with same name as source function is always ambiguous > ---------------------------------------------------------------------- > > Key: TEIID-5976 > URL: https://issues.redhat.com/browse/TEIID-5976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > If we have both a virtual schema and a source schema function with the same name, f1, then issuing a query like: > select v.f1()... > will always report that v.f1 is ambiguous because in the resolving of the function the logic at one point disregards the schema. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5976) virtual function with same name as source function is always ambiguous

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5976: ------------------------------------- Summary: virtual function with same name as source function is always ambiguous Key: TEIID-5976 URL: https://issues.redhat.com/browse/TEIID-5976 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 15.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4594) Add ability to read Parquet Files

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4594?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-4594: --------------------------------------- [~adityamanglam] I'm not sure yet why, but I can't assign this to you in the Teiid JIRA. Another thing to start looking at is the excel translator - it is the most translator in that it works off of a file source and provides the teiid table representation of an excel file: https://github.com/teiid/teiid/tree/master/connectors/file/translator-excel > Add ability to read Parquet Files > --------------------------------- > > Key: TEIID-4594 > URL: https://issues.redhat.com/browse/TEIID-4594 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > > Integration with Parquet files on Gluster is an important requirement. RADAnalytics will be accessing data from Parquet which is a common file format for Spark. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-213) We have strange behavior with aliases

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-213?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-213: ---------------------------------------- If the SOQL columns are qualified you get one set of results, and if they are not qualified you get another. That does seem like a SF bug. > Can we find any method to generate this SOQL? Not in any built-in path other than utilizing the native query procedure. Have you seen any reference to a salesforce issue about this? Does it only happen with __kav objects? If we understand better why this is happening it would help in determining a built-in solution. > We have strange behavior with aliases > ------------------------------------- > > Key: TEIIDSB-213 > URL: https://issues.redhat.com/browse/TEIIDSB-213 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Renat Eskenin > Priority: Major > Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png > > > We have two SOQL > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > > SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a WHERE a.Language = 'it' LIMIT 5 > This SOQL requests get different responses from SF because in second request we have alias for table. > It is mystics from SF (we made bug in sf) > How we can call > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > in Teiid without aliases? -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-213) We have strange behavior with aliases

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-213?page=com.atlassian.jira.plug... ] Renat Eskenin commented on TEIIDSB-213: --------------------------------------- SOQL {code} SELECT Regular_Articles__kav.ArticleNumber, Regular_Articles__kav.Id, Regular_Articles__kav.KnowledgeArticleId, Regular_Articles__kav.Language FROM Regular_Articles__kav {code} in SF get so strange data set with only one language (en_US). But {code} SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav {code} get all data with all languages. Can we fine any method to generate this SOQL SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav from SQL by Teiid? > We have strange behavior with aliases > ------------------------------------- > > Key: TEIIDSB-213 > URL: https://issues.redhat.com/browse/TEIIDSB-213 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Renat Eskenin > Priority: Major > Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png > > > We have two SOQL > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > > SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a WHERE a.Language = 'it' LIMIT 5 > This SOQL requests get different responses from SF because in second request we have alias for table. > It is mystics from SF (we made bug in sf) > How we can call > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > in Teiid without aliases? -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-213) We have strange behavior with aliases

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-213?page=com.atlassian.jira.plug... ] Renat Eskenin edited comment on TEIIDSB-213 at 6/26/20 2:07 PM: ---------------------------------------------------------------- SOQL {code} SELECT Regular_Articles__kav.ArticleNumber, Regular_Articles__kav.Id, Regular_Articles__kav.KnowledgeArticleId, Regular_Articles__kav.Language FROM Regular_Articles__kav {code} in SF get so strange data set with only one language (en_US). But {code} SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav {code} get all data with all languages. Can we find any method to generate this SOQL SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav from SQL by Teiid? was (Author: i3draven): SOQL {code} SELECT Regular_Articles__kav.ArticleNumber, Regular_Articles__kav.Id, Regular_Articles__kav.KnowledgeArticleId, Regular_Articles__kav.Language FROM Regular_Articles__kav {code} in SF get so strange data set with only one language (en_US). But {code} SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav {code} get all data with all languages. Can we fine any method to generate this SOQL SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav from SQL by Teiid? > We have strange behavior with aliases > ------------------------------------- > > Key: TEIIDSB-213 > URL: https://issues.redhat.com/browse/TEIIDSB-213 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Renat Eskenin > Priority: Major > Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png > > > We have two SOQL > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > > SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a WHERE a.Language = 'it' LIMIT 5 > This SOQL requests get different responses from SF because in second request we have alias for table. > It is mystics from SF (we made bug in sf) > How we can call > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > in Teiid without aliases? -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-213) We have strange behavior with aliases

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-213?page=com.atlassian.jira.plug... ] Renat Eskenin edited comment on TEIIDSB-213 at 6/26/20 2:08 PM: ---------------------------------------------------------------- SOQL {code} SELECT Regular_Articles__kav.ArticleNumber, Regular_Articles__kav.Id, Regular_Articles__kav.KnowledgeArticleId, Regular_Articles__kav.Language FROM Regular_Articles__kav {code} in SF get so strange data set with only one language (en_US). But {code} SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav {code} get all data with all languages. Can we find any method to generate this SOQL? SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav from SQL by Teiid? was (Author: i3draven): SOQL {code} SELECT Regular_Articles__kav.ArticleNumber, Regular_Articles__kav.Id, Regular_Articles__kav.KnowledgeArticleId, Regular_Articles__kav.Language FROM Regular_Articles__kav {code} in SF get so strange data set with only one language (en_US). But {code} SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav {code} get all data with all languages. Can we find any method to generate this SOQL SELECT ArticleNumber, Id,KnowledgeArticleId, Language FROM Regular_Articles__kav from SQL by Teiid? > We have strange behavior with aliases > ------------------------------------- > > Key: TEIIDSB-213 > URL: https://issues.redhat.com/browse/TEIIDSB-213 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Renat Eskenin > Priority: Major > Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png > > > We have two SOQL > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > > SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a WHERE a.Language = 'it' LIMIT 5 > This SOQL requests get different responses from SF because in second request we have alias for table. > It is mystics from SF (we made bug in sf) > How we can call > SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5 > in Teiid without aliases? -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2020