December 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5856) Teiid generate wrong request to salesforce

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIID-5856?page=com.atlassian.jira.plugin... ] Renat Eskenin commented on TEIID-5856: -------------------------------------- References it is relations :) It is true SOQL SELECT Account.BillingCountry__c, Account.Name FROM Contact LIMIT 1 But in another SQL we have wrong SOQL. I did wrote example: SQL (one level of nested join) originalLicense.ReplacementLicenseID__c = replacementLicense.Id It is relation ReplacementLicenseID__r {code} SELECT originalLicense.Id,originalLicense.Status__c,originalLicense.ReplacementLicenseID__c,originalLicense.LicenseId__c,originalLicense.vlic_Contract_Number__c,replacementLicense.LicenseId__c as replacementLicenseId ,replacementLicense.LicenseId__c as replacementLicenseLicenseId FROM Product_License__c originalLicense LEFT OUTER JOIN /*+ MAKEDEP */ Product_License__c replacementLicense ON originalLicense.ReplacementLicenseID__c = replacementLicense.Id where originalLicense.vlic_Contract_Number__c = :contractNumber {code} But generated SOQL have two separate requests: {code} [2019-11-28 08:24:03,575 GMT] DEBUG [salesforce-failover-facade,,,] [salesforce-failover-facade-56f467f5f8-q8mml] org.teiid.CONNECTOR [Worker0_QueryProcessorQueue0]: salesforce.87EGAL91ieOh.87EGAL91ieOh.0.2: Executing Query: SELECT Product_License__c.ReplacementLicenseID__c, Product_License__c.Id, Product_License__c.Status__c, Product_License__c.LicenseId__c, Product_License__c.vlic_Contract_Number__c FROM Product_License__c WHERE Product_License__c.vlic_Contract_Number__c = '11111aaaaa' {code} Second real request {code} [2019-11-28 08:24:04,025 GMT] DEBUG [salesforce-failover-facade,,,] [salesforce-failover-facade-56f467f5f8-q8mml] org.teiid.CONNECTOR [Worker0_QueryProcessorQueue1]: salesforce.87EGAL91ieOh.87EGAL91ieOh.0.3: Incoming Query: SELECT Product_License__c.Id, Product_License__c.LicenseId__c FROM Product_License__c WHERE Product_License__c.Id = 'asdasdasdadasdasd {code} It is "wrong plan", but now i understand to this true plan but wrong generated SOQL by salesforce translator. > Teiid generate wrong request to salesforce > ------------------------------------------ > > Key: TEIID-5856 > URL: https://issues.jboss.org/browse/TEIID-5856 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Environment: spring-boot teiid salesforce-connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When i call request to salesforce teiid get very long wrong request and then OOM, because teiid request all data in salesforce object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-145) Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-145?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-145: --------------------------------- Sprint: DV Sprint 56 > Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis > ---------------------------------------------------------------- > > Key: TEIIDSB-145 > URL: https://issues.jboss.org/browse/TEIIDSB-145 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To match the version with Syndesis, move the Spring Boot to 2.1.6.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-143) SAP Gateway returns 406

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-143?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-143: --------------------------------- Sprint: DV Sprint 55, DV Sprint 56 (was: DV Sprint 55) > SAP Gateway returns 406 > ----------------------- > > Key: TEIIDSB-143 > URL: https://issues.jboss.org/browse/TEIIDSB-143 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 2 hours, 30 minutes > Time Spent: 2 hours > Remaining Estimate: 30 minutes > > After the header fix TEIIDSB-134 for some reason SAP responds with a 406 - it doesn't like having multiple accept header values at least when used through our spring boot rest support. Just sending application/xml works as expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-136) Allow translator properties to be set via application.properties

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-136?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-136: --------------------------------- Sprint: DV Sprint 56 > Allow translator properties to be set via application.properties > ---------------------------------------------------------------- > > Key: TEIIDSB-136 > URL: https://issues.jboss.org/browse/TEIIDSB-136 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core, datasource, examples > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > When using a vdb-less deployment, import/model properties can be set from spring.datasource. or spring.xa.datasource. properties. However translator properties cannot. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-133) Add "jdbc-simple" and "jdbc-ansi" translators

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-133?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-133: --------------------------------- Sprint: DV Sprint 54, DV Sprint 56 (was: DV Sprint 54) > Add "jdbc-simple" and "jdbc-ansi" translators > --------------------------------------------- > > Key: TEIIDSB-133 > URL: https://issues.jboss.org/browse/TEIIDSB-133 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Priority: Critical > Fix For: 1.3.0 > > > Add support for the "jdbc-simple" and "jdbc-ansi" translators. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5835?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5835: -------------------------------- Sprint: DV Sprint 56 > Upgrade Apache Olingo to a final version of 4.7 > ----------------------------------------------- > > Key: TEIID-5835 > URL: https://issues.jboss.org/browse/TEIID-5835 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.0 > > > Teiid needs to upgrade from the olingo 4.7 SNAPSHOT. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-123) Provide support for Amazon Athena

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-123?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-123: --------------------------------- Sprint: DV Sprint 56 > Provide support for Amazon Athena > --------------------------------- > > Key: TEIIDSB-123 > URL: https://issues.jboss.org/browse/TEIIDSB-123 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Provide the translator support for Amazon Athena -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-124) Provide translator support Infinispan

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-124?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-124: --------------------------------- Sprint: DV Sprint 54, DV Sprint 56 (was: DV Sprint 54) > Provide translator support Infinispan > ------------------------------------- > > Key: TEIIDSB-124 > URL: https://issues.jboss.org/browse/TEIIDSB-124 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Provide translator support for Infinispan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5780) Support certificate based authentication into Teiid pg

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5780?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5780: --------------------------------------- Rather than doing this as something specific for just pg, I've been looking at incorporating this as a general change. It would naturally move to the SSLAwareChannelHandler. There with an onConnection event we can get the principal and the certificate chain. We can attempt an authentication call, which would require the realm to accept a x509 certificate as the credential (still need to validate that and that the Certificate[] is the expected credential). With keycloak direct auth needs to be configured with x509 support and we need make a request that adds the certificates as header values: https://www.keycloak.org/docs/4.8/server_admin/#adding-x-509-client-certi... However it does seem like we would need a new authentication type to indicate that a username/password check is optional. Obviously adding as a general feature does not support the specific case of admin access for materialization, but it at least makes the inclusion much simpler if we want to do that. In any case this needs to be pulled out of 13.0. > Support certificate based authentication into Teiid pg > ------------------------------------------------------ > > Key: TEIID-5780 > URL: https://issues.jboss.org/browse/TEIID-5780 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > To support the pg connection into Teiid we will do something like: > - require a pg secure port using the service signing certificate: TEIIDSB-90 TEIIDSB-92 > -- one clarification is that we must document how to make the pg cert dominant if both pg and jdbc secure are used > TODO: > - configure the pg instance to have a service signing certificate and trust the Teiid service signing certificate. If that trust seems too difficult we can just configure the connection to trust all. > - configure the pg connection to Teiid to use the pg service signing certificate as the client certificate > - trust the pg service signing certificate at the teiid service - we need hostname validation to be enabled and the Teiid server to map the service host name to an authenticated user (this could possibly be generalized via keycloak support to more users). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5858) Orcale collation issue with Teiid 9.1.1

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5858?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5858: --------------------------------------- Yes, there can be issues with sorting expectations and columns that have specific collations. If assumeMatchingCollation is set to false that is typically enough to inhibit pushdown of sorts for merge sort join processing. If it is false and the collationLocale matches what is reported by the translator collectionLocale, then the sort will still be pushed down. Can you provide the final plan that shows what sort is being pushed? > Orcale collation issue with Teiid 9.1.1 > --------------------------------------- > > Key: TEIID-5858 > URL: https://issues.jboss.org/browse/TEIID-5858 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 9.1.1 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Priority: Major > > One of customers run into this following error: > org.teiid.core.TeiidComponentException: TEIID31202 Detected that an already sorted set of values was not in the expected order (typically UTF-16 / UCS-2). Please check the translator settings to ensure character columns used for joining are sorted as expected. > And they were trying to join multiple oracle databases together. And they are running Teiid 9.1.1 > It seems like I need to change the collation. And I tried to change those values, but it didn't seem to do anything. > org.teiid.requireTeiidCollation > org.teiid.collationLocale > org.teiid.assumeMatchingCollation > Here is how we create the tables in Oracle: > CREATE TABLE "DWH_MSFL"."MW_CATEGORY" CREATE TABLE "DWH_MSFL"."MW_CATEGORY" ( "CAT_ID" NUMBER(*,0), "CAT_TITLE" VARCHAR2(255 CHAR), "CAT_TITLE_ORIGIN" VARCHAR2(255 CHAR), "CAT_PAGES" NUMBER(*,0), "CAT_SUBCATS" NUMBER(*,0), "CAT_FILES" NUMBER(*,0) ) SEGMENT CREATION IMMEDIATE PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "DWH_MSFL" ; > > > -------------------------- > > CREATE TABLE "DWH_MSFL"."MW_CATEGORYLINKS" CREATE TABLE "DWH_MSFL"."MW_CATEGORYLINKS" ( "CL_FROM" NUMBER(*,0), "CL_TO" VARCHAR2(255 CHAR), "CL_SORTKEY" VARCHAR2(230 CHAR), "CL_TIMESTAMP" TIMESTAMP (0), "CL_SORTKEY_PREFIX" VARCHAR2(255 CHAR), "CL_COLLATION" VARCHAR2(32 CHAR), "CL_TYPE" VARCHAR2(10 CHAR) ) SEGMENT CREATION IMMEDIATE PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "DWH_MSFL" ; > Notwithstanding, can't the issue somehow be related to categorylinks>category relation or Column-Level Collation (CI_COLLATION)which is set to Uppercase(see insert to categorylinks table in DWH_MSFL.sql). We have an issue exactly with a category and title column(CAT_TITLE) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019