June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Bram Gadeyne (JIRA)

Bram Gadeyne created TEIID-3511: ----------------------------------- Summary: usage of BITAND function in exists statement results in duplicate rows Key: TEIID-3511 URL: https://issues.jboss.org/browse/TEIID-3511 Project: Teiid Issue Type: Bug Affects Versions: 8.9.1 Reporter: Bram Gadeyne Assignee: Steven Hawkins I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3510) Move the Embedded examples into separate repository

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3510: ---------------------------------- Summary: Move the Embedded examples into separate repository Key: TEIID-3510 URL: https://issues.jboss.org/browse/TEIID-3510 Project: Teiid Issue Type: Feature Request Components: Embedded Affects Versions: 8.11 Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 8.11 Create a separate repository for embedded examples, define a maven BOM file for the dependencies management of all examples, and prepare for further refinement like add xa datasources support, add OAuth/REST service, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3508) External mat view without ttl behavior

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3508?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3508: --------------------------------------- do you want to take this one? > External mat view without ttl behavior > -------------------------------------- > > Key: TEIID-3508 > URL: https://issues.jboss.org/browse/TEIID-3508 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > When no ttl is specified an external mat view will not be loaded by the management service - but the on vdb start / stop scripts will be run. We should figure out if/when an initial load should take place. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3509) Consolidate internal and external materialization management

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3509?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3509: ---------------------------------- Fix Version/s: 8.12 > Consolidate internal and external materialization management > ------------------------------------------------------------ > > Key: TEIID-3509 > URL: https://issues.jboss.org/browse/TEIID-3509 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12 > > > - Currently there separate SYSADMIN procedures for internal and external materialization to refresh them, we need to provide single set > - The management of the (usage of status table) is not fully utilized by the internal materialization this needs to addressed such that both external and internal use this table to keep track of load status -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3501) IN clause - teradata does not support "CAST( ... AS ...)" statement in "IN(...)"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3501?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3501. ----------------------------------- Resolution: Done Switched to use DATE '...', TIME '...', etc. literals, which are acceptable in an in predicate. > IN clause - teradata does not support "CAST( ... AS ...)" statement in "IN(...)" > -------------------------------------------------------------------------------- > > Key: TEIID-3501 > URL: https://issues.jboss.org/browse/TEIID-3501 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Environment: teradata version: 15 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The teradata DB does not support CAST statement in IN. Query (1), teradata exception (2), source specific command (3), query that teradata accepts (4). > (1) SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.TimeStampValue IN (convert('2000-01-01 00:00:12.0', timestamp), convert('2000-01-01 00:00:45.0', timestamp)) ORDER BY IntKey > (2) SELECT g_0.intkey AS c_0 FROM smalla AS g_0 WHERE g_0.timestampvalue IN (cast('2000-01-01 00:00:12.0' AS TIMESTAMP(6)), cast('2000-01-01 00:00:45.0' AS TIMESTAMP(6))) ORDER BY 1 > (3) SELECT g_0.intkey AS c_0 FROM smalla AS g_0 WHERE g_0.timestampvalue IN ('2000-01-01 00:00:12.0', '2000-01-01 00:00:45.0') ORDER BY 1 > (4) Caused by: java.sql.SQLException: [Teradata Database] [TeraJDBC 15.10.00.05] [Error 3706] [SQLState 42000] Syntax error: expected something between ')' and ','. > at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDatabaseSQLException(ErrorFactory.java:308) > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3474) Inconsistent results of RIGHT function for different datasources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3474?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3474: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1221051|https://bugzilla.redhat.com/show_bug.cgi?id=1221051] from NEW to MODIFIED > Inconsistent results of RIGHT function for different datasources > ---------------------------------------------------------------- > > Key: TEIID-3474 > URL: https://issues.jboss.org/browse/TEIID-3474 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > The RIGHT function returns different results for different datasources. Some of those results are inconsistent with definition of the RIGHT(x,y) function. > ======= > +*Query: SELECT intkey, RIGHT(intkey, 1) FROM table ORDER BY intkey*+ > *Teradata, SQLServer, Sybase, Ingres, MySQL, Oracle (this result is OK):* > 0 0 > 1 1 > 2 2 > ... > 10 0 > 11 1 > ... > 100 0 > 101 1 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " > ===== > +*Query:SELECT intkey, RIGHT(intkey, 2) FROM table ORDER BY intkey*+ > *SQLServer, Sybase, Ingress, MySQL, Teradata (this result is OK):* > 0 0 > 1 1 > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Oracle:* > 0 <null> > 1 <null> > 2 <null> > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3487) preparedstatement leaks in odbc

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3487?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3487: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1227330|https://bugzilla.redhat.com/show_bug.cgi?id=1227330] from NEW to MODIFIED > preparedstatement leaks in odbc > ------------------------------- > > Key: TEIID-3487 > URL: https://issues.jboss.org/browse/TEIID-3487 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > There are several places where preparedstatements are being created and never closed by the odbc logic. And since we don't have garbage collection based cleanup, this can lead to a build up on the statementimpl. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3359) Allow more control over odata layer caching

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3359: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1227333|https://bugzilla.redhat.com/show_bug.cgi?id=1227333] from ASSIGNED to MODIFIED > Allow more control over odata layer caching > ------------------------------------------- > > Key: TEIID-3359 > URL: https://issues.jboss.org/browse/TEIID-3359 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11 > > > The caching is always performed at a user level and for each query. Consumers may need to localize the caching affect only to paging results and scope only to that interaction, rather than for all users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3359) Allow more control over odata layer caching

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3359: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1227333|https://bugzilla.redhat.com/show_bug.cgi?id=1227333] from NEW to ASSIGNED > Allow more control over odata layer caching > ------------------------------------------- > > Key: TEIID-3359 > URL: https://issues.jboss.org/browse/TEIID-3359 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11 > > > The caching is always performed at a user level and for each query. Consumers may need to localize the caching affect only to paging results and scope only to that interaction, rather than for all users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3501) IN clause - teradata does not support "CAST( ... AS ...)" statement in "IN(...)"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3501?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3501: --------------------------------------- I had forgotten that TEIID-2064 covers the odd in behavior, so all we have to do is use a better literal form. > IN clause - teradata does not support "CAST( ... AS ...)" statement in "IN(...)" > -------------------------------------------------------------------------------- > > Key: TEIID-3501 > URL: https://issues.jboss.org/browse/TEIID-3501 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Environment: teradata version: 15 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The teradata DB does not support CAST statement in IN. Query (1), teradata exception (2), source specific command (3), query that teradata accepts (4). > (1) SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.TimeStampValue IN (convert('2000-01-01 00:00:12.0', timestamp), convert('2000-01-01 00:00:45.0', timestamp)) ORDER BY IntKey > (2) SELECT g_0.intkey AS c_0 FROM smalla AS g_0 WHERE g_0.timestampvalue IN (cast('2000-01-01 00:00:12.0' AS TIMESTAMP(6)), cast('2000-01-01 00:00:45.0' AS TIMESTAMP(6))) ORDER BY 1 > (3) SELECT g_0.intkey AS c_0 FROM smalla AS g_0 WHERE g_0.timestampvalue IN ('2000-01-01 00:00:12.0', '2000-01-01 00:00:45.0') ORDER BY 1 > (4) Caused by: java.sql.SQLException: [Teradata Database] [TeraJDBC 15.10.00.05] [Error 3706] [SQLState 42000] Syntax error: expected something between ')' and ','. > at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDatabaseSQLException(ErrorFactory.java:308) > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015