July 2020 - teiid-issues - Jboss List Archives

[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 commented on TEIID-5988: --------------------------------------- Teiid is used transitively under Teiid Spring Boot. The simplest change you could make is to use the teiid spring boot master 1.6 snapshot version. > 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 Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5988?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIID-5988: -------------------------------------- We used in projects {code} <dependency> <groupId>org.teiid</groupId> <artifactId>spring-data-salesforce</artifactId> <version>1.5.1</version> </dependency> <dependency> <groupId>org.teiid</groupId> <artifactId>teiid-spring-boot-starter</artifactId> <version>1.5.1</version> </dependency> {code} What version need to use this changes? > 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-5985) Disinformational exception messages when Salesforce is down

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5985?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIID-5985: -------------------------------------- Please give me maven dependency with this fixes. How I can update our experimental project to use this fixes? > 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-5995) Status table not found in mvn status function when schema is hidden

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5995?focusedWorklogId=12451761&pag... ] Steven Hawkins logged work on TEIID-5995: ----------------------------------------- Author: Steven Hawkins Created on: 17/Jul/20 12:58 PM Start Date: 17/Jul/20 12:58 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 1 hour (was: 3 hours) Time Spent: 2 hours Worklog Id: (was: 12451761) > Status table not found in mvn status function when schema is hidden > ------------------------------------------------------------------- > > Key: TEIID-5995 > URL: https://issues.redhat.com/browse/TEIID-5995 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > Original Estimate: 3 hours > Time Spent: 2 hours > Remaining Estimate: 1 hour > > Related to TEIID-5943 which only addressed the problem for admin sql calls, the visibility rules when hidden metadata is not resolvable prevent the mvn status function sql from seeing hidden schema. This is because the mvn status function and the embedded connection are running in the context of the user query. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5995) Status table not found in mvn status function when schema is hidden

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5995?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5995. ----------------------------------- Fix Version/s: 15.0 14.0.1 Resolution: Done Added a check in request for derived connections and will use the design time metadata instead. The other fix of admin queries being able to see anything is still valid - although we could consider combining the two. The admin check though allows for the potential of still having session scoped metadata so I'm leaving them separate for now. > Status table not found in mvn status function when schema is hidden > ------------------------------------------------------------------- > > Key: TEIID-5995 > URL: https://issues.redhat.com/browse/TEIID-5995 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > > Related to TEIID-5943 which only addressed the problem for admin sql calls, the visibility rules when hidden metadata is not resolvable prevent the mvn status function sql from seeing hidden schema. This is because the mvn status function and the embedded connection are running in the context of the user query. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5995) Status table not found in mvn status function when schema is hidden

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5995?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5995: ---------------------------------- Original Estimate: 3 hours Remaining Estimate: 3 hours > Status table not found in mvn status function when schema is hidden > ------------------------------------------------------------------- > > Key: TEIID-5995 > URL: https://issues.redhat.com/browse/TEIID-5995 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Related to TEIID-5943 which only addressed the problem for admin sql calls, the visibility rules when hidden metadata is not resolvable prevent the mvn status function sql from seeing hidden schema. This is because the mvn status function and the embedded connection are running in the context of the user query. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5968) enabled=true flag not visible in xa-datasource

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5968?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5968: --------------------------------------- > Will i be able to take just the admin api build from latest version of teiid , as we are using Teiid standalone and admin api as seperate jars Yes, they are generally compatible across versions. > enabled=true flag not visible in xa-datasource > ---------------------------------------------- > > Key: TEIID-5968 > URL: https://issues.redhat.com/browse/TEIID-5968 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 13.1.2, 14.0.1 > > Original Estimate: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > While creating a XA-Datasource using admin Api, enabled="true" paramter is not set and is not visible in standalone-teiid.xml, have to add it manually. > > Because of this flag not set, connection pooling is not working and teiid is creating more connections than max-pool-size mentioned -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5968) enabled=true flag not visible in xa-datasource

by Manoj Majumdar (Jira)

[ https://issues.redhat.com/browse/TEIID-5968?page=com.atlassian.jira.plugi... ] Manoj Majumdar commented on TEIID-5968: --------------------------------------- Will i be able to take just the admin api build from latest version of teiid , as we are using Teiid standalone and admin api as seperate jars > enabled=true flag not visible in xa-datasource > ---------------------------------------------- > > Key: TEIID-5968 > URL: https://issues.redhat.com/browse/TEIID-5968 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 13.1.2, 14.0.1 > > Original Estimate: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > While creating a XA-Datasource using admin Api, enabled="true" paramter is not set and is not visible in standalone-teiid.xml, have to add it manually. > > Because of this flag not set, connection pooling is not working and teiid is creating more connections than max-pool-size mentioned -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5995) Status table not found in mvn status function when schema is hidden

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5995: ------------------------------------- Summary: Status table not found in mvn status function when schema is hidden Key: TEIID-5995 URL: https://issues.redhat.com/browse/TEIID-5995 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Related to TEIID-5943 which only addressed the problem for admin sql calls, the visibility rules when hidden metadata is not resolvable prevent the mvn status function sql from seeing hidden schema. This is because the mvn status function and the embedded connection are running in the context of the user query. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5994) If capabilities are not available not pushing a function masks the problem

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5994?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5994. ----------------------------------- Resolution: Done Addressed in master just for the narrow case of the must pushdown function. There are likely other similar scenarios where we may be masking a capabilities/connection issue with a planning exception - if we encounter those we can either add this check to those places or look toward adding a general check via catching query planner exceptions. However the latter seems like it wouldn't work unless we start associating the originating model (if applicable) with the exception. > If capabilities are not available not pushing a function masks the problem > -------------------------------------------------------------------------- > > Key: TEIID-5994 > URL: https://issues.redhat.com/browse/TEIID-5994 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > In a situation that requires subexpression pushing, for example: > select virtual_func(source_func(col)) from tbl > such that source_func must be pushed. The actual exception will be about the expression not being able to be pushed, and not about the capabilities being unavailable - which could only be seen at a debug level. -- 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