June 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Assigned: (TEIID-1664) Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected BQT results

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1664?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-1664: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected BQT results > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1664 > URL: https://issues.jboss.org/browse/TEIID-1664 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Attachments: QT_teradata12_Push.vdb > > > Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected results. The following query should be returning 22 rows but 0 rows are returned. > SELECT intkey, booleanvalue FROM BQT1.SmallA WHERE LTRIM(BQT1.SmallA.BooleanValue) = 'true' ORDER BY intkey > However, if the LTRIM is removed like (SELECT intkey, booleanvalue FROM BQT1.SmallA WHERE BQT1.SmallA.BooleanValue = 'true' ORDER BY intkey) 22 rows are returned. > This should be logged against Teiid 7.4.1 > VDB attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1651) Due to a change in the JDBC spec on how the use of "AS" in the select statement will now be returned in the getColumnLabel of the ResultSetMetadata, Teiid must provide backwards support

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1651?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-1651: ------------------------------- Fix Version/s: 7.4.1 > Due to a change in the JDBC spec on how the use of "AS" in the select statement will now be returned in the getColumnLabel of the ResultSetMetadata, Teiid must provide backwards support > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-1651 > URL: https://issues.jboss.org/browse/TEIID-1651 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 7.4.1 > > > Teiid has already applied a fix to support the JDBC spec change for when an alias is used in the select clause. The spec change says the "AS" name will now be returned when getColumnLabel() is called, instead of getColumnName(). Unfortunately, this breaks backwards compatibility. To resolve the issue, the JDBC driver, to provide support for backwards compatibility, can allow the user to specify the useJDBC4ColumnNameAndLabelSemantics=true (default is false) property on the url (this is the recommended spec property). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1660) EDS BQT Queries failing on SqlServer 2005 with SQLServerException "Type DATE is not a defined system type"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1660?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1660. ----------------------------------- Assignee: Steven Hawkins Fix Version/s: 7.4.1 Resolution: Done This was a regression from TEIID-1303 > EDS BQT Queries failing on SqlServer 2005 with SQLServerException "Type DATE is not a defined system type" > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1660 > URL: https://issues.jboss.org/browse/TEIID-1660 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 7.4.1 > > > 17 EDS BQT queries are failing when using SqlServer 2005 as a source. SQLServerException "Type DATE is not a defined system type". Below is an example. They are passing in SqlServer 2008. VDB is attached. > Query: SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.DateValue IN (convert('2000-01-12', date), convert('2000-02-02', date)) ORDER BY IntKey > Log: > 2011-06-28 10:35:18,130 DEBUG [org.teiid.CONNECTOR] (Worker16_QueryProcessorQueue136) Source-specific command: SELECT TOP 100 cast(g_0.IntKey AS int) AS c_0 FROM SmallA g_0 WHERE cast(replace(convert(varchar, g_0.DateValue, 102), '.', '-') AS datetime) IN (CAST('2000-01-12' AS DATE), CAST('2000-02-02' AS DATE)) ORDER BY c_0 > 2011-06-28 10:35:18,179 DEBUG [org.teiid.COMMAND_LOG] (Worker16_QueryProcessorQueue136) ERROR SRC COMMAND: endTime=2011-06-28 10:35:18.179 requestID=Q0JsTZlYNGm0.23 sourceCommandID=1 txID=null modelName=Source connectorBindingName=sqlserver sessionID=Q0JsTZlYNGm0 principal=user@teiid-security finalRowCount=null > 2011-06-28 10:35:18,179 WARN [org.teiid.CONNECTOR] (Worker16_QueryProcessorQueue136) Connector worker process failed for atomic-request=Q0JsTZlYNGm0.23.1.21 > [JDBCExecutionException] 243: Error Code:243 Message:'Type DATE is not a defined system type.' error executing statement(s): [Prepared Values: [] SQL: SELECT TOP 100 cast(g_0.IntKey AS int) AS c_0 FROM SmallA g_0 WHERE cast(replace(convert(varchar, g_0.DateValue, 102), '.', '-') AS datetime) IN (CAST('2000-01-12' AS DATE), CAST('2000-02-02' AS DATE)) ORDER BY c_0] > 1 [SQLServerException]Type DATE is not a defined system type. > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338) > at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:197) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Type DATE is not a defined system type. > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338) > at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:281) > at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) > ... 13 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1660) EDS BQT Queries failing on SqlServer 2005 with SQLServerException "Type DATE is not a defined system type"

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1660?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3135 to TEIID-1660: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1660 (was: SOA-3135) Affects Version/s: 7.4.1 (was: 5.2.0 GA) Component/s: Query Engine (was: EDS) Security: (was: Public) > EDS BQT Queries failing on SqlServer 2005 with SQLServerException "Type DATE is not a defined system type" > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1660 > URL: https://issues.jboss.org/browse/TEIID-1660 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Warren Gibson > > 17 EDS BQT queries are failing when using SqlServer 2005 as a source. SQLServerException "Type DATE is not a defined system type". Below is an example. They are passing in SqlServer 2008. VDB is attached. > Query: SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.DateValue IN (convert('2000-01-12', date), convert('2000-02-02', date)) ORDER BY IntKey > Log: > 2011-06-28 10:35:18,130 DEBUG [org.teiid.CONNECTOR] (Worker16_QueryProcessorQueue136) Source-specific command: SELECT TOP 100 cast(g_0.IntKey AS int) AS c_0 FROM SmallA g_0 WHERE cast(replace(convert(varchar, g_0.DateValue, 102), '.', '-') AS datetime) IN (CAST('2000-01-12' AS DATE), CAST('2000-02-02' AS DATE)) ORDER BY c_0 > 2011-06-28 10:35:18,179 DEBUG [org.teiid.COMMAND_LOG] (Worker16_QueryProcessorQueue136) ERROR SRC COMMAND: endTime=2011-06-28 10:35:18.179 requestID=Q0JsTZlYNGm0.23 sourceCommandID=1 txID=null modelName=Source connectorBindingName=sqlserver sessionID=Q0JsTZlYNGm0 principal=user@teiid-security finalRowCount=null > 2011-06-28 10:35:18,179 WARN [org.teiid.CONNECTOR] (Worker16_QueryProcessorQueue136) Connector worker process failed for atomic-request=Q0JsTZlYNGm0.23.1.21 > [JDBCExecutionException] 243: Error Code:243 Message:'Type DATE is not a defined system type.' error executing statement(s): [Prepared Values: [] SQL: SELECT TOP 100 cast(g_0.IntKey AS int) AS c_0 FROM SmallA g_0 WHERE cast(replace(convert(varchar, g_0.DateValue, 102), '.', '-') AS datetime) IN (CAST('2000-01-12' AS DATE), CAST('2000-02-02' AS DATE)) ORDER BY c_0] > 1 [SQLServerException]Type DATE is not a defined system type. > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338) > at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:197) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Type DATE is not a defined system type. > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338) > at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:281) > at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) > ... 13 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1641) In org.teiid.jdbc.StatementImpl, as there have been no batched updates the batchedUpdates member hasn't been instantiated so clearBatch() throws a NPE.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1641?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1641: ---------------------------------- Fix Version/s: 7.5 > In org.teiid.jdbc.StatementImpl, as there have been no batched updates the batchedUpdates member hasn't been instantiated so clearBatch() throws a NPE. > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1641 > URL: https://issues.jboss.org/browse/TEIID-1641 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.4 > Reporter: Debbie Steigner > Priority: Blocker > Fix For: 7.4.1, 7.5 > > > In org.teiid.jdbc.StatementImpl, as there have been no batched updates the batchedUpdates member hasn't been instantiated so clearBatch() throws a NPE. > I have added a simple if (batchedUpdates != null) in clearBatch() on the Teiid 7.4 driver sources, please make this addition to EDS 5.2 driver. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1654) CLONE - EDS - Node returns 0 rows for cached view when other node had it loaded and leaves cluster

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1654?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1654: ---------------------------------- Fix Version/s: 7.5 > CLONE - EDS - Node returns 0 rows for cached view when other node had it loaded and leaves cluster > -------------------------------------------------------------------------------------------------- > > Key: TEIID-1654 > URL: https://issues.jboss.org/browse/TEIID-1654 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > Using an internal materialized view in EDS 5.1 with CP2, a node which never had a copy of an IMV cache will return 0 rows when it should be querying the source in situations where another node in the cluster had cached the IMV but is no longer in the cluster -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1657) CLONE - EDS - refreshMatView does not work correctly for an internal materialized view when clustering is enabled

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1657?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1657: ---------------------------------- Fix Version/s: 7.5 > CLONE - EDS - refreshMatView does not work correctly for an internal materialized view when clustering is enabled > ----------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1657 > URL: https://issues.jboss.org/browse/TEIID-1657 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > The refreshMatView works as expected in a single node environment with 'teiid-cache-manager-jboss-beans-rename-me.xml'. Still in a single node environment, that function no longer refreshes the data with "teiid-cache-manager-jboss-beans.xml" enabled. > To recreate: > 1. Start up an EDS instance with a vdb deployed which has an internal materialized view (IMV). > 2. Query SYSADMIN.MATVIEWS and verify LoadState = "NEEDS_LOADING" > 3. Query the IMV to populate the cache. > 4. Query SYSADMIN.MATVIEWS and verify LoadState = "LOADED". Note the value of the 'Updated' column > 5. run "CALL SYSADMIN.refreshMatView('view name',false)" > 6. Query SYSADMIN.MATVIEWS and verify LoadState = "LOADED". Note the value of the 'Updated' column > 7. Query the IMV to see if it pulls from the source or cache > Expected results: Steps 3 and 5 should trigger queries to the source. Step 7 should pull from the cache without going back to the source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-97) add proper SQLState for timeout/cancel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-97?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-97: -------------------------------- Fix Version/s: 7.5 > add proper SQLState for timeout/cancel > -------------------------------------- > > Key: TEIID-97 > URL: https://issues.jboss.org/browse/TEIID-97 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.4.1, 7.5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Query timeouts/cancel should set the SQLState to 57014 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1452) Add pagination capabilities to the LDAP connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1452?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1452. ----------------------------------- Resolution: Duplicate Issue dup of TEIID-1659 > Add pagination capabilities to the LDAP connector > ------------------------------------------------- > > Key: TEIID-1452 > URL: https://issues.jboss.org/browse/TEIID-1452 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > > Active Directory (AD) appears to limit results to a max size of 1000. Any search against AD that returns more than 1000 results requires paging to be used to view the additional results [1]. In order for the LDAP connector to be useful within AD it would be helpful to have pagination capabilities. > [1] http://msdn.microsoft.com/en-us/library/ms180880(v=vs.90).aspx -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1659) Support pagination of LDAP results when retrieving from Active Directory

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1659?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3129 to TEIID-1659: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1659 (was: SOA-3129) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: LDAP Connector (was: EDS) Security: (was: Public) > Support pagination of LDAP results when retrieving from Active Directory > ------------------------------------------------------------------------ > > Key: TEIID-1659 > URL: https://issues.jboss.org/browse/TEIID-1659 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 7.1.1 > Environment: EDS 5.1. LDAP connection factory/translator. Active Directory as LDAP provider. > Reporter: Ken Johnson > > Active Directory has a setting MaxPageSize that limits the number of records of query results returned in a batch. The EDS LDAP connector/translator should support this setting so it can page through the results and retrieve all results. Not just up to MaxPageSize. Ideally this would be a configurable parameter that the user must set to match the MaxPageSize value on the AD server. For more info: http://support.microsoft.com/kb/315071. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 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 2011