July 2020 - teiid-issues - Jboss List Archives

[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 updated TEIIDSB-213: ----------------------------------- Original Estimate: 5 hours Remaining Estimate: 5 hours Story Points: 1 Sprint: DV Sprint 66 > 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 > Assignee: Steven Hawkins > Priority: Major > Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png > > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > 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)

5 years, 8 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 reassigned TEIIDSB-213: -------------------------------------- Assignee: Steven Hawkins > 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 > Assignee: Steven Hawkins > 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)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5987) salesforce self join involving implicit null check on parentid field not working

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5987?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5987: --------------------------------------- Likely related to the parent handling described in https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sos... > salesforce self join involving implicit null check on parentid field not working > -------------------------------------------------------------------------------- > > Key: TEIID-5987 > URL: https://issues.redhat.com/browse/TEIID-5987 > Project: Teiid > Issue Type: Bug > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > I'm not sure about the full scope of this issue. In testing TEIIDSB-213 I can see that a query such as: > select a1.id from Account a1 inner join account a2 on a1.parentid = a2.id > which results in the source query with the implicit null check: > SELECT Id FROM Account WHERE ParentId != NULL > actually returns results, but no are expected. > The explicit non-join query query > select a1.id from Account a1 where a1.parentid is not null > result in: > SELECT Id FROM Account WHERE ParentId != NULL > but returns no results > So there is something in the join handling that is not working as expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5987) salesforce self join involving implicit null check on parentid field not working

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5987: ------------------------------------- Summary: salesforce self join involving implicit null check on parentid field not working Key: TEIID-5987 URL: https://issues.redhat.com/browse/TEIID-5987 Project: Teiid Issue Type: Bug Reporter: Steven Hawkins Assignee: Steven Hawkins I'm not sure about the full scope of this issue. In testing TEIIDSB-213 I can see that a query such as: select a1.id from Account a1 inner join account a2 on a1.parentid = a2.id which results in the source query with the implicit null check: SELECT Id FROM Account WHERE ParentId != NULL actually returns results, but no are expected. The explicit non-join query query select a1.id from Account a1 where a1.parentid is not null result in: SELECT Id FROM Account WHERE ParentId != NULL but returns no results So there is something in the join handling that is not working as expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-126) Provide source support Amazon SimpleDB

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-126?focusedWorklogId=12451722&pa... ] Steven Hawkins logged work on TEIIDSB-126: ------------------------------------------ Author: Steven Hawkins Created on: 13/Jul/20 8:16 AM Start Date: 13/Jul/20 8:15 AM Worklog Time Spent: 3 hours Work Description: Time spent reviewing and updating the wildfly modules. Issue Time Tracking ------------------- Remaining Estimate: 1 hour (was: 4 hours) Time Spent: 3 hours Worklog Id: (was: 12451722) > Provide source support Amazon SimpleDB > -------------------------------------- > > Key: TEIIDSB-126 > URL: https://issues.redhat.com/browse/TEIIDSB-126 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Mudit Jain > Priority: Major > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 1 hour > > Provide translator support for Amazon SimpleDB -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-126) Provide source support Amazon SimpleDB

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-126?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-126: ----------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours Story Points: 1 Sprint: DV Sprint 66 > Provide source support Amazon SimpleDB > -------------------------------------- > > Key: TEIIDSB-126 > URL: https://issues.redhat.com/browse/TEIIDSB-126 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Mudit Jain > Priority: Major > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Provide translator support for Amazon SimpleDB -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5986) S3 translator flat file parser can not support unicode

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5986?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5986: ---------------------------------- Fix Version/s: 15.0 > S3 translator flat file parser can not support unicode > ------------------------------------------------------ > > Key: TEIID-5986 > URL: https://issues.redhat.com/browse/TEIID-5986 > Project: Teiid > Issue Type: Feature Request > Reporter: Rui Wang > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > > I saw there is one ticket on Unicode support for flat file. Seems I can not config it in V14 if I am using java api to create my VDB xml. Steven mentioned it is migrated to S3 translater. Could you pls enhance it in latest Teiid version > > [https://issues.redhat.com/browse/TEIID-4340?page=com.atlassian.jira.plugi...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5986) S3 translator flat file parser can not support unicode

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5986?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5986: --------------------------------------- To clarify the s3 translator supports an encoding property that can utilize any of the JRE built-in charsets, including utf-8 and utf-16. There are several common ones missing that the engine has support for such as utf-8-bom, HEX, and BASE64. A workaround is to use getFile instead of getTextFile and use the engine function to_chars http://teiid.github.io/teiid-documents/master/content/reference/r_string-... to convert the blob to a clob with the engine supported encodings. > S3 translator flat file parser can not support unicode > ------------------------------------------------------ > > Key: TEIID-5986 > URL: https://issues.redhat.com/browse/TEIID-5986 > Project: Teiid > Issue Type: Feature Request > Reporter: Rui Wang > Assignee: Steven Hawkins > Priority: Major > > I saw there is one ticket on Unicode support for flat file. Seems I can not config it in V14 if I am using java api to create my VDB xml. Steven mentioned it is migrated to S3 translater. Could you pls enhance it in latest Teiid version > > [https://issues.redhat.com/browse/TEIID-4340?page=com.atlassian.jira.plugi...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5986) S3 translator flat file parser can not support unicode

by Rui Wang (Jira)

Rui Wang created TEIID-5986: ------------------------------- Summary: S3 translator flat file parser can not support unicode Key: TEIID-5986 URL: https://issues.redhat.com/browse/TEIID-5986 Project: Teiid Issue Type: Feature Request Reporter: Rui Wang Assignee: Steven Hawkins I saw there is one ticket on Unicode support for flat file. Seems I can not config it in V14 if I am using java api to create my VDB xml. Steven mentioned it is migrated to S3 translater. Could you pls enhance it in latest Teiid version [https://issues.redhat.com/browse/TEIID-4340?page=com.atlassian.jira.plugi...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 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: --------------------------------------- > What do you mean by this Steven Hawkins? The first sentence The hive metastore is a common metadata source for hive, presto. spark, etc. The create table syntax is quite extensive: https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#Langu... - it is not expected that we would support all of options. Alternatively we could consider requiring/leveraging a metastore instance, similar to presto, rather than coming up with our own metadata representation. A single source, meaning an s3 bucket or a filesystem location, could have multiple sets of paraquet files each representing a separate table. > 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)

5 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2020