September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2477) Standardize and correct jdbc database version comparisons

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2477?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2477. --------------------------------- > Standardize and correct jdbc database version comparisons > --------------------------------------------------------- > > Key: TEIID-2477 > URL: https://issues.jboss.org/browse/TEIID-2477 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > The simple string comparison of versions is not correct across version numbers of differing digits (10 is not higher than 9). Generally the field needs standardized as well since for example we use the year designations for SQL Server but the driver reported version numbers will be the actual software versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2545) Fix hibernate-on-top-of-teiid quick start

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2545?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2545. --------------------------------- > Fix hibernate-on-top-of-teiid quick start > ----------------------------------------- > > Key: TEIID-2545 > URL: https://issues.jboss.org/browse/TEIID-2545 > Project: Teiid > Issue Type: Sub-task > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > > Fix the .rar deployment based on the new EAP deployment requirements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2552) Upgrade javacc-maven-plugin from 2.4.1 to 2.6

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2552?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2552. --------------------------------- > Upgrade javacc-maven-plugin from 2.4.1 to 2.6 > --------------------------------------------- > > Key: TEIID-2552 > URL: https://issues.jboss.org/browse/TEIID-2552 > Project: Teiid > Issue Type: Component Upgrade > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4.1, 8.5 > > > javacc-maven-plugin 2.6 is needed due to other components are already using 2.6. > Also, its already been determined that Teiid fails to compile when 2.6 is used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2438) Hive Connector not working in Teiid 8

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2438?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2438. --------------------------------- > Hive Connector not working in Teiid 8 > ------------------------------------- > > Key: TEIID-2438 > URL: https://issues.jboss.org/browse/TEIID-2438 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.3 > Environment: Any > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Fix For: 8.4 > > > Hive Connector is not working. It throws exception [2] when the query is submitted. Bug was introduced in commit 98456d89aa6c04028dbf971bddc322b3e3a3978b in patch for [1]. > Problem is metadata loading. The HiveMetadataProcessor adds strings "null" around table names because the patch [1] calls common JDBCConnector's addTable. That method then uses "quote" field (which is null) to quote the table name and sets this to nameInSource property. > [1] https://issues.jboss.org/browse/TEIID-2281 > [2] > {code:title=Exception|borderStyle=solid} > 14:17:16,870 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=s9z3Rn3JAr7e.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 10 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.col FROM nullmyfilesnull g_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:257) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:457) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:177) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:174) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_07] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_07] > at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:250) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.2.0.Final.jar:8.2.0.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] > Caused by: java.sql.SQLException: Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull' > at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:177) > at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:140) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84) > ... 13 more > Caused by: HiveServerException(message:Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull', errorCode:10, SQLState:42000) > at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494) > at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480) > at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78) > at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116) > at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103) > at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175) > ... 16 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2448) Oracle driver translation error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2448?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2448. --------------------------------- > Oracle driver translation error > ------------------------------- > > Key: TEIID-2448 > URL: https://issues.jboss.org/browse/TEIID-2448 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Even procedures without resultsets have ?= added to them by the Oracle translator when it assumes the oracle driver is being used (the default). This will lead to a source error complaining that the function cannot be found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2503) XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2503?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2503. --------------------------------- > XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error" > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2503 > URL: https://issues.jboss.org/browse/TEIID-2503 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: EAP6.1Alpha and Teiid8.4Alpha > Reporter: Warren Gibson > Assignee: Steven Hawkins > Priority: Minor > Attachments: QT_PostgreSQL91_Push.vdb, SERVER.log > > > The following queries are producing TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error. > The queries were returning expected query results in SOA-P5.3.1 release. However, when testing them with EAP 6.1Alpha and > Teiid 8.4Alpha they are returning the "Unable to evaluate "INPUT".nextKey" message. This is occuring on Postgres91, Oracle10,11,11RAC, Mysql55, Teradata, and Greenplum data sources. > I isolated "SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key" and ran a test to produce a log entry which > is attached. If you need other testing artifacts such as VDB please let me know. > SELECT * FROM XQTNestedDoc.testBoundTempTable > SELECT * FROM XQTNestedDoc.testExcludeFromDoc ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testOptimizableTempTable ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testRootTempTable ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testNested2Document ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testNestedDocument ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testSimpleDocument ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testSimpleTempTable ORDER BY recursiveroot.key -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2432. --------------------------------- > Dynamic VDB isLoading state doesnt change on fail > ------------------------------------------------- > > Key: TEIID-2432 > URL: https://issues.jboss.org/browse/TEIID-2432 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.4 > > > I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB deployment is finished. > In my case the VDB dataSource is not available. I can see in the server log that the deployment fails immediately, but the isLoading state remains true. > Is this in error, or what status should we be checking? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2544) Fix dynamicvdb-dataroles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2544?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2544. --------------------------------- > Fix dynamicvdb-dataroles > ------------------------ > > Key: TEIID-2544 > URL: https://issues.jboss.org/browse/TEIID-2544 > Project: Teiid > Issue Type: Sub-task > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > > Fix the .rar deployment based on the new EAP deployment requirements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2468) teiid script should return null if an intermediate object is null

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2468?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2468. --------------------------------- > teiid script should return null if an intermediate object is null > ----------------------------------------------------------------- > > Key: TEIID-2468 > URL: https://issues.jboss.org/browse/TEIID-2468 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > A script such as foo.bar.z will throw an npe if bar is null, but return null if foo is null. for consistency null should always be returned when any reference in the script chain is null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2505) MultiArrayOutputStream computes count incorrectly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2505?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2505. --------------------------------- > MultiArrayOutputStream computes count incorrectly > ------------------------------------------------- > > Key: TEIID-2505 > URL: https://issues.jboss.org/browse/TEIID-2505 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4 > > > The count computed may not be correct when the bytes written exceeds the primary array size. This impacts teiid in client to server messaging when the client message exceeds 1 < 15 bytes - which is uncommon, but can happen with extremely large sql, large directly bound (not stream) values, etc. > The exception produced will be shown as "Connection reset". The server will log the exception as an EOFException - but at a detail level since we assume that IOExceptions can be logged at a lower level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013