July 2020 - teiid-issues - Jboss List Archives

[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 resolved TEIID-5986. ----------------------------------- Resolution: Done Changed to use charsetutils for the charset lookup. > 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)

4 years, 6 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: ---------------------------------- Component/s: Misc. Connectors Original Estimate: 30 minutes Remaining Estimate: 30 minutes Story Points: 0.1 Sprint: DV Sprint 66 > 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 > Components: Misc. Connectors > Reporter: Rui Wang > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5985) Disinformational exception messages when Salesforce is down

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5985?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5985. ----------------------------------- Resolution: Done We'll simply use the exception class name as the message if none is provided. Especially for sf exceptions the class name conveys the particular problem. This is vastly simpler than trying to introduce our own messages for each scenario. > Disinformational exception messages when Salesforce is down > ----------------------------------------------------------- > > Key: TEIID-5985 > URL: https://issues.redhat.com/browse/TEIID-5985 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When Salesforce is down we have Exceptions as > {code} > TEIID30504 salesforce: null; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: null > {code} > It is all information in exception about caused problem :( -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5985) Disinformational exception messages when Salesforce is down

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5985?focusedWorklogId=12451724&pag... ] Steven Hawkins logged work on TEIID-5985: ----------------------------------------- Author: Steven Hawkins Created on: 13/Jul/20 2:21 PM Start Date: 13/Jul/20 2:21 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12451724) > Disinformational exception messages when Salesforce is down > ----------------------------------------------------------- > > Key: TEIID-5985 > URL: https://issues.redhat.com/browse/TEIID-5985 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > When Salesforce is down we have Exceptions as > {code} > TEIID30504 salesforce: null; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: null > {code} > It is all information in exception about caused problem :( -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5985) Disinformational exception messages when Salesforce is down

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5985?page=com.atlassian.jira.plugi... ] Work on TEIID-5985 started by Steven Hawkins. --------------------------------------------- > Disinformational exception messages when Salesforce is down > ----------------------------------------------------------- > > Key: TEIID-5985 > URL: https://issues.redhat.com/browse/TEIID-5985 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > > When Salesforce is down we have Exceptions as > {code} > TEIID30504 salesforce: null; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: null > {code} > It is all information in exception about caused problem :( -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5985) Disinformational exception messages when Salesforce is down

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5985?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5985: ---------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours Story Points: 0.5 Sprint: DV Sprint 66 > Disinformational exception messages when Salesforce is down > ----------------------------------------------------------- > > Key: TEIID-5985 > URL: https://issues.redhat.com/browse/TEIID-5985 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When Salesforce is down we have Exceptions as > {code} > TEIID30504 salesforce: null; nested exception is org.teiid.jdbc.TeiidSQLException: TEIID30504 salesforce: null > {code} > It is all information in exception about caused problem :( -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5988) We have strange behavior with aliases

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5988?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5988. ----------------------------------- Fix Version/s: 15.0 Resolution: Done Changed the soql generation strategy to only qualify when a specific parent name is set. Otherwise we are relying upon the context of the table in the immediate from clause. From what I can see since no correlation is supported this should work - and does for the join scenarios we have captured in our tests. This change also addresses the dubious query generation for the testSelfJoinOuterParentToChild case - it now has no qualification on the inner id column. [~i3draven] if these changes work for you and there is a specific currently supported other branch, 13.x or 14.x you would like to see them on let us know. > We have strange behavior with aliases > ------------------------------------- > > Key: TEIID-5988 > URL: https://issues.redhat.com/browse/TEIID-5988 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > 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)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5988) We have strange behavior with aliases

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5988?focusedWorklogId=12451723&pag... ] Steven Hawkins logged work on TEIID-5988: ----------------------------------------- Author: Steven Hawkins Created on: 13/Jul/20 1:50 PM Start Date: 13/Jul/20 1:50 PM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 5 hours) Time Spent: 5 hours Worklog Id: (was: 12451723) > We have strange behavior with aliases > ------------------------------------- > > Key: TEIID-5988 > URL: https://issues.redhat.com/browse/TEIID-5988 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png > > Original Estimate: 5 hours > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > 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)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5988) We have strange behavior with aliases

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5988?page=com.atlassian.jira.plugi... ] Steven Hawkins moved TEIIDSB-213 to TEIID-5988: ----------------------------------------------- Project: Teiid (was: Teiid Spring Boot) Key: TEIID-5988 (was: TEIIDSB-213) Component/s: Salesforce Connector (was: datasource) > We have strange behavior with aliases > ------------------------------------- > > Key: TEIID-5988 > URL: https://issues.redhat.com/browse/TEIID-5988 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > 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)

4 years, 6 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 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)

4 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2020