October 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5034) Couchbase SUBSTRING function returns null when reaches end of string

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5034?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5034: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1484915|https://bugzilla.redhat.com/show_bug.cgi?id=1484915] from MODIFIED to ON_QA > Couchbase SUBSTRING function returns null when reaches end of string > -------------------------------------------------------------------- > > Key: TEIID-5034 > URL: https://issues.jboss.org/browse/TEIID-5034 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Couchbase return null when y points after the string end in SUBSTRING(VALUE, x, y). That's not what is expected from Teiid. > Teiid: > {code:sql|title=query1} > SELECT SUBSTRING('49',1, 10) > {code} > || expr1 || > || 49 || > Couchbase pushdown: > {code:sql|title=query2} > SELECT SUBSTRING(BQT1.SmallA.intkey, 1, 10) FROM BQT1.SmallA WHERE IntKey=49 > {code} > || expr1 || > || <null> || > {code:title=teiid-command.log} > 16:18:57,156 INFO [org.teiid.COMMAND_LOG] (New I/O worker #2) QE2ZpDa/Btt5 START USER COMMAND: startTime=2017-08-24 16:18:57.156 requestID=QE2ZpDa/Btt5.124 txID=null sessionID=QE2ZpDa/Btt5 applicationName=JDBC principal=user@teiid-security vdbName=couchbase vdbVersion=1 sql=SELECT SUBSTRING(BQT1.SmallA.intkey, 1, 10) FROM BQT1.SmallA WHERE IntKey=49 > 16:18:57,160 DEBUG [org.teiid.COMMAND_LOG] (Worker39_QueryProcessorQueue353) QE2ZpDa/Btt5 START DATA SRC COMMAND: startTime=2017-08-24 16:18:57.16 requestID=QE2ZpDa/Btt5.124 sourceCommandID=0 executionID=85 txID=null modelName=Couchbase_small translatorName=couchbase sessionID=QE2ZpDa/Btt5 principal=user@teiid-security sql=SELECT SUBSTRING(convert(Couchbase_small.SmallA.IntKey, string), 1, 10) FROM Couchbase_small.SmallA WHERE Couchbase_small.SmallA.IntKey = 49 > 16:18:57,160 DEBUG [org.teiid.COMMAND_LOG] (Worker39_QueryProcessorQueue353) QE2ZpDa/Btt5 SOURCE SRC COMMAND: endTime=2017-08-24 16:18:57.16 requestID=QE2ZpDa/Btt5.124 sourceCommandID=0 executionID=85 txID=null modelName=Couchbase_small translatorName=couchbase sessionID=QE2ZpDa/Btt5 principal=user@teiid-security sourceCommand=[SELECT SUBSTR(TOSTRING(`$cb_c1_IntKey`), 1, 10) FROM `dvqe_small` `$cb_t1` LET `$cb_c1_IntKey` = `$cb_t1`.`IntKey` WHERE `$cb_c1_IntKey` = 49 AND `$cb_t1`.`type` = 'SmallA'] > 16:18:57,449 DEBUG [org.teiid.COMMAND_LOG] (Worker38_QueryProcessorQueue354) QE2ZpDa/Btt5 END SRC COMMAND: endTime=2017-08-24 16:18:57.449 requestID=QE2ZpDa/Btt5.124 sourceCommandID=0 executionID=85 txID=null modelName=Couchbase_small translatorName=couchbase sessionID=QE2ZpDa/Btt5 principal=user@teiid-security finalRowCount=1 cpuTime(ns)=1213042 > 16:18:57,456 INFO [org.teiid.COMMAND_LOG] (Worker38_QueryProcessorQueue355) QE2ZpDa/Btt5 END USER COMMAND: endTime=2017-08-24 16:18:57.456 requestID=QE2ZpDa/Btt5.124 txID=null sessionID=QE2ZpDa/Btt5 principal=user@teiid-security vdbName=couchbase vdbVersion=1 finalRowCount=1 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4812) Processor is not exiting the join as soon as it's determined one side contains 0 rows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4812?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4812: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1492613|https://bugzilla.redhat.com/show_bug.cgi?id=1492613] from MODIFIED to ON_QA > Processor is not exiting the join as soon as it's determined one side contains 0 rows > ------------------------------------------------------------------------------------- > > Key: TEIID-4812 > URL: https://issues.jboss.org/browse/TEIID-4812 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.8.6_3, 8.7.11.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.10.6_3, 8.12.x-6.4, 9.2.2 > > > There is an issue with the processor during a join, it doesn't exit the join as soon as it's determined that one side of the join returns 0 rows. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4459) Convert project semi-joins to (dependent) join queries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4459?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4459: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1492815|https://bugzilla.redhat.com/show_bug.cgi?id=1492815] from MODIFIED to ON_QA > Convert project semi-joins to (dependent) join queries > ------------------------------------------------------ > > Key: TEIID-4459 > URL: https://issues.jboss.org/browse/TEIID-4459 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.x-6.4 > > > In many situations subqueries in the where clause can be planned as semi-joins. The same logic should be updated to handle the select clause. > This will also help ensure better performance with odata generated array_agg queries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-5106?page=com.atlassian.jira.plugin... ] sameer P commented on TEIID-5106: --------------------------------- Thanks. > Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid. > -------------------------------------------------------------------------- > > Key: TEIID-5106 > URL: https://issues.jboss.org/browse/TEIID-5106 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 10.0 > > > In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: > {code:java} > 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 > at org.teiid.metadata.Schema.addTable(Schema.java:51) > at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) > at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.jboss.VDBService$6.run(VDBService.java:341) > at org.teiid.jboss.VDBService$7.run(VDBService.java:392) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5106?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5106: --------------------------------------- TEIID-5115 has been spawned for general handling, but given low priority. > Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid. > -------------------------------------------------------------------------- > > Key: TEIID-5106 > URL: https://issues.jboss.org/browse/TEIID-5106 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 10.0 > > > In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: > {code:java} > 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 > at org.teiid.metadata.Schema.addTable(Schema.java:51) > at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) > at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.jboss.VDBService$6.run(VDBService.java:341) > at org.teiid.jboss.VDBService$7.run(VDBService.java:392) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5115) Add a general property to handle case-insensitive naming collisions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5115?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5115: ---------------------------------- Component/s: Misc. Connectors Description: This is a request to generally handle case-sensitive name collisions. See also TEIID-5006 (was: In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: {code:java} 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 at org.teiid.metadata.Schema.addTable(Schema.java:51) at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) at org.teiid.jboss.VDBService$6.run(VDBService.java:341) at org.teiid.jboss.VDBService$7.run(VDBService.java:392) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) {code} ) Fix Version/s: 10.x (was: 10.0) Summary: Add a general property to handle case-insensitive naming collisions (was: Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.) Priority: Minor (was: Major) > Add a general property to handle case-insensitive naming collisions > ------------------------------------------------------------------- > > Key: TEIID-5115 > URL: https://issues.jboss.org/browse/TEIID-5115 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector, Misc. Connectors > Reporter: sameer P > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.x > > > This is a request to generally handle case-sensitive name collisions. See also TEIID-5006 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5115) Add a general property to handle case-insensitive naming collisions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5115?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5115: ---------------------------------- Description: This is a request to generally handle case-sensitive name collisions. See also TEIID-5106 (was: This is a request to generally handle case-sensitive name collisions. See also TEIID-5006) > Add a general property to handle case-insensitive naming collisions > ------------------------------------------------------------------- > > Key: TEIID-5115 > URL: https://issues.jboss.org/browse/TEIID-5115 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector, Misc. Connectors > Reporter: sameer P > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.x > > > This is a request to generally handle case-sensitive name collisions. See also TEIID-5106 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5115) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5115: ------------------------------------- Summary: Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid. Key: TEIID-5115 URL: https://issues.jboss.org/browse/TEIID-5115 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: sameer P Assignee: Steven Hawkins Fix For: 10.0 In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: {code:java} 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 at org.teiid.metadata.Schema.addTable(Schema.java:51) at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) at org.teiid.jboss.VDBService$6.run(VDBService.java:341) at org.teiid.jboss.VDBService$7.run(VDBService.java:392) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5114) Correct JDBCMetdataProcessor name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5114?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5114. ----------------------------------- Resolution: Done Corrected the name and introduced a deprecated class. > Correct JDBCMetdataProcessor name > --------------------------------- > > Key: TEIID-5114 > URL: https://issues.jboss.org/browse/TEIID-5114 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > JDBCMetdataProcessor should be JDBCMetadataProcessor instead. To resolve this as a non-breaking change the old class name will still exist and extend JDBCMetadataProcessor, but be deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5114) Correct JDBCMetdataProcessor name

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5114: ------------------------------------- Summary: Correct JDBCMetdataProcessor name Key: TEIID-5114 URL: https://issues.jboss.org/browse/TEIID-5114 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 JDBCMetdataProcessor should be JDBCMetadataProcessor instead. To resolve this as a non-breaking change the old class name will still exist and extend JDBCMetadataProcessor, but be deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017