August 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1899) Getting Assertion when running running Inner Merge Join

by Van Halbert (JIRA)

Van Halbert created TEIID-1899: ---------------------------------- Summary: Getting Assertion when running running Inner Merge Join Key: TEIID-1899 URL: https://issues.jboss.org/browse/TEIID-1899 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Steven Hawkins When running the following query, it causing an ASSERTION (see attached log): SELECT COUNT(*) AS CNT FROM (SELECT ORDERS.O_ORDERKEY, ORDERS.O_ORDERDATE, ORDERS.O_CLERK, CUSTOMER.C_CUSTKEY, CUSTOMER.C_NAME, CUSTOMER.C_ACCTBAL FROM TPCR01_PostgreSQLVirt.ORDERS, TPCR01_OracleVirt.CUSTOMER WHERE (CUSTOMER.C_CUSTKEY = ORDERS.O_CUSTKEY) AND (ORDERS.O_ORDERDATE < '1992-01-05 00:00:00') AND (CUSTOMER.C_ACCTBAL < 9514.5)) AS T Note: this doesn't fail when SELECT COUNT(*) is added -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
19
0 / 0

[JBoss JIRA] (TEIID-2031) Overloaded functions are not supported via ddl / Schema object

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2031: ------------------------------------- Summary: Overloaded functions are not supported via ddl / Schema object Key: TEIID-2031 URL: https://issues.jboss.org/browse/TEIID-2031 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 The Schema object expects unique function names, but we need to allow multiple functions with the same name to support overloading. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2044) Column name aliases are not processed for MIN and MAX functions (but are for AVG)

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2044: ---------------------------------- Summary: Column name aliases are not processed for MIN and MAX functions (but are for AVG) Key: TEIID-2044 URL: https://issues.jboss.org/browse/TEIID-2044 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7.1 Environment: SOA-P 5.3 ER2 Reporter: Paul Nittel Assignee: Steven Hawkins Found this while validating data sources. If I enter this SQL: SELECT MIN(col) AS AAA, AVG(col) AS BBB, MAX(col) AS CCC FROM table, the columns are named col, BBB, col. They should be AAA, BBB, CCC. Found this was the case with the jdbc-simple and oracle translators -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1960) Client recieving java.lang.IndexOutOfBoundsException in

by Tim Bruce (JIRA)

Tim Bruce created TEIID-1960: -------------------------------- Summary: Client recieving java.lang.IndexOutOfBoundsException in Key: TEIID-1960 URL: https://issues.jboss.org/browse/TEIID-1960 Project: Teiid Issue Type: Bug Environment: JBoss 5.1.0.GA Teiid Engine 7.6.0.Final 64-bit Java 1.7.0 Reporter: Tim Bruce Assignee: Steven Hawkins 01 Mar 2012 21:37:21,891 GMT ERROR [org.teiid.TRANSPORT] (Worker225_QueryProcessorQueue13539) Unhandled exception, closing client instance java.lang.IndexOutOfBoundsException: Index: 3, Size: 3 at java.util.ArrayList.rangeCheck(ArrayList.java:615) at java.util.ArrayList.get(ArrayList.java:393) at org.teiid.client.BatchSerializer.writeIsNullData(BatchSerializer.java:226) at org.teiid.client.BatchSerializer$ColumnSerializer.writeColumn(BatchSerializer.java:262) at org.teiid.client.BatchSerializer.writeBatch(BatchSerializer.java:542) at org.teiid.client.ResultsMessage.writeExternal(ResultsMessage.java:277) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1463) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1434) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1194) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:363) at org.teiid.net.socket.Message.writeExternal(Message.java:56) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1463) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1434) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1194) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:363) at org.teiid.transport.ObjectEncoder.handleDownstream(ObjectEncoder.java:115) at org.jboss.netty.channel.Channels.write(Channels.java:611) at org.jboss.netty.channel.Channels.write(Channels.java:578) at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:258) at org.teiid.transport.SSLAwareChannelHandler$ObjectChannelImpl.write(SSLAwareChannelHandler.java:94) at org.teiid.transport.SocketClientInstance.send(SocketClientInstance.java:82) at org.teiid.transport.ServerWorkItem.sendResult(ServerWorkItem.java:127) at org.teiid.transport.ServerWorkItem$1.onCompletion(ServerWorkItem.java:99) at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130) at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37) at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:674) at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:528) at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:174) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:149) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:370) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:287) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:215) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:232) 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:1121) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614) at java.lang.Thread.run(Thread.java:769) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
15
0 / 0

[JBoss JIRA] (TEIID-1997) Add the ability to support Oracle synonyms

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1997?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1997. --------------------------------- > Add the ability to support Oracle synonyms > ------------------------------------------- > > Key: TEIID-1997 > URL: https://issues.jboss.org/browse/TEIID-1997 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 6.0.0 > Reporter: Erica Langhi > Priority: Minor > > Currently Teiid Designer doesn't provide the ability > to recognize synonyms. > It would be very beneficial to add this feature as synonyms > are commonly used -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2021) Fail the VDB deployment when translator is not available

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2021: ----------------------------------- Summary: Fail the VDB deployment when translator is not available Key: TEIID-2021 URL: https://issues.jboss.org/browse/TEIID-2021 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 VDBDeployer checks for the override translator types, however it does not check for the base translators that are configured in the VDB. So, when a VDB with unknown translator is deployed, it gets deployed but never exposes any error information as to why the VDB is not "active". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
9
0 / 0

[JBoss JIRA] (TEIID-2032) Add ability to add OPTIONS on Key types in DDL

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2032: ----------------------------------- Summary: Add ability to add OPTIONS on Key types in DDL Key: TEIID-2032 URL: https://issues.jboss.org/browse/TEIID-2032 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 In the DDL based matadata the extended properties through OPTIONS keyword can be specified on the Tables, columns,procedures and functions. Extend this feature to include the Primary Keys and Foreign keys etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (TEIID-2019) Remove all references to "javax.xml.bind" classes in the Teiid and support stream based xml

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2019: ----------------------------------- Summary: Remove all references to "javax.xml.bind" classes in the Teiid and support stream based xml Key: TEIID-2019 URL: https://issues.jboss.org/browse/TEIID-2019 Project: Teiid Issue Type: Task Components: Common Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1980) JDBC connection QueryTimeout property appears to be ignored

by Paul Nittel (JIRA)

Paul Nittel created TEIID-1980: ---------------------------------- Summary: JDBC connection QueryTimeout property appears to be ignored Key: TEIID-1980 URL: https://issues.jboss.org/browse/TEIID-1980 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Paul Nittel Assignee: Steven Hawkins While testing an EDS patch, I tried to constrain a query by adding ;QueryTimeout=1 to my JDBC connection string. This had no apparent effect. (The query--a repeated UNION ALL of huge tables, followed by a descending ORDER BY--takes over 30 seconds.) I also tried 3 and 10 second timeouts, but all allowed the query to continue to completion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
11
0 / 0

[JBoss JIRA] (TEIID-2008) Allow client max object size to be settable

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2008: ------------------------------------- Summary: Allow client max object size to be settable Key: TEIID-2008 URL: https://issues.jboss.org/browse/TEIID-2008 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 The default 32 MB for max object size may be too small in custom scenarios or when there are numerous warnings attached to results. This should be a settable property via the client settings properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2012