October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1320) Oracle datetime columns as timestamp have invalid tostring

by Steven Hawkins (JIRA)

Oracle datetime columns as timestamp have invalid tostring ---------------------------------------------------------- Key: TEIID-1320 URL: https://jira.jboss.org/browse/TEIID-1320 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 We are looking for native type of date, but that needs to be case insensitive. And to prevent any issues we should cast to timestamp just to be safe in case we can't use native type. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1312) Default stored procedure params should not show up in string form

by Steven Hawkins (JIRA)

Default stored procedure params should not show up in string form ----------------------------------------------------------------- Key: TEIID-1312 URL: https://jira.jboss.org/browse/TEIID-1312 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.1.1 After being resolved stored procedure default parameter values are being shown in the toString. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1202) JOPR Console VDB View has couple usability issues

by Ramesh Reddy (JIRA)

JOPR Console VDB View has couple usability issues -------------------------------------------------- Key: TEIID-1202 URL: https://jira.jboss.org/browse/TEIID-1202 Project: Teiid Issue Type: Quality Risk Components: Jopr Plugin Reporter: Ramesh Reddy Assignee: Ted Jones Fix For: 7.1 1) Full Name is not required. Name and version is suffice 2) Status {UP, DOWN} is verbose and useful IMO. Status is already is shown by red X on the left nav. Also, in the summary page we are calling it "ACTIVE". This needs to be tidy up. 3) Connection Type - needs more explanation in the description. With out it is going confuse users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1316) XML encoding of a blob is not properly detected.

by Steven Hawkins (JIRA)

XML encoding of a blob is not properly detected. ------------------------------------------------ Key: TEIID-1316 URL: https://jira.jboss.org/browse/TEIID-1316 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 If a blob is passed to the xmlparse function and is parsed as a document, it is not properly picking up the encoding specified in the xml declaration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1210) Add support for non-unique indexes for materialized view tables

by Steve Hawkins (JIRA)

Add support for non-unique indexes for materialized view tables --------------------------------------------------------------- Key: TEIID-1210 URL: https://jira.jboss.org/browse/TEIID-1210 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Currently only a primary key index is created for internal materialized view tables. It would be good to allow non-unique indexes to be created for all other index/unique constraints on the view. This would also allow the user to approximate a function based index by adding an additional column to the view projecting the evaluated function. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1310) SYS.VDBResources table is set as a non-system-owned table - should be isSystem = true

by Paul Nittel (JIRA)

SYS.VDBResources table is set as a non-system-owned table - should be isSystem = true ------------------------------------------------------------------------------------- Key: TEIID-1310 URL: https://jira.jboss.org/browse/TEIID-1310 Project: Teiid Issue Type: Bug Affects Versions: 7.1.1 Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 7.1.1 If you execute this query: select name, isSystem from sys.tables You will find the VDBResources table is listed with isSystem = false. It should be true as this is owned by the system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1295) Multisource updates affecting multiple sources returns wrong update count

by Steven Hawkins (JIRA)

Multisource updates affecting multiple sources returns wrong update count ------------------------------------------------------------------------- Key: TEIID-1295 URL: https://jira.jboss.org/browse/TEIID-1295 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.2 The multisource plan to process converter uses union all even for insert/update/delete scenarios, which returns the wrong update count (only the first) to the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1308) Multi-source vdb table's metadata does not report the implicit "source_name" column

by Ramesh Reddy (JIRA)

Multi-source vdb table's metadata does not report the implicit "source_name" column ----------------------------------------------------------------------------------- Key: TEIID-1308 URL: https://jira.jboss.org/browse/TEIID-1308 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 7.2 When user enquires metadata on a multi-source vdb's table it does not report that it has extra "SOURCE_NAME" column, however when you view the data from the table it includes the extra table. The metadata needs to be correctly reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1317) Limit keyword causes class cast exception running query against DB2 translator

by Howard Abrams (JIRA)

Limit keyword causes class cast exception running query against DB2 translator ------------------------------------------------------------------------------ Key: TEIID-1317 URL: https://jira.jboss.org/browse/TEIID-1317 Project: Teiid Issue Type: Bug Affects Versions: 7.1, 7.0, 6.2.0 Reporter: Howard Abrams Assignee: Steven Hawkins When running a query that uses the limit keyword against a DB2 database/translator, teiid will throw the exception below (From the 7.1 codebase, but I got the same exception a while back playing with 7.0 as well as 6.2). The same query against the same schema in a different database (H2 for example) works fine. It appears it also works fin on DB2 if you leave off the starting rowing from the expression. Examples: /*works on H2*/ SELECT * FROM MYSCHEMA.FOO LIMIT 0,10 /*fails on DB2*/ SELECT * FROM MYSCHEMA.FOO LIMIT 0,10 /*fails on DB2*/ SELECT * FROM MYSCHEMA.FOO LIMIT 10,10 /*works on DB2*/ SELECT * FROM MYSCHEMA.FOO LIMIT 10 java.lang.ClassCastException: org.teiid.language.Function cannot be cast to org.teiid.language.Literal at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:719) at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:211) at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:130) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:215) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:181) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:53) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:89) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:86) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1321) Error message when connecting to missing VDB is misleading (makes it sound like it exists)

by Paul Nittel (JIRA)

Error message when connecting to missing VDB is misleading (makes it sound like it exists) ------------------------------------------------------------------------------------------ Key: TEIID-1321 URL: https://jira.jboss.org/browse/TEIID-1321 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.1.1 Environment: Fedora 12, SOA-P ER3 Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 7.1.1 I was using the simpleclient to query an XML document model, but misspelled the name of the VDB. The error I received was that the subject VDB was not active. Actually, it didn't exist and that distinction could have saved me a bunch of time trying to figure out why it appeared to be active, but wasn't. Here's an example (this VDB does not exist): ./run.sh localhost 31000 barfingToad "select * from booksdoc.booksetmixeddocument" Executing using the TeiidDriver Oct 25, 2010 12:45:07 PM org.teiid.jdbc.SocketProfile connect SEVERE: Could not create connection [ConnectionException]Remote org.teiid.client.security.LogonException: VDB "barfingToad" version "latest" is not in "active" status. 1 [LogonException]Remote org.teiid.client.security.LogonException: VDB "barfingToad" version "latest" is not in "active" status. 2 [TeiidSecurityException]Remote org.teiid.dqp.service.SessionServiceException: VDB "barfingToad" version "latest" is not in "active" status. at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:143) at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:94) at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:310) at org.teiid.jdbc.SocketProfile.createConnection(SocketProfile.java:104) at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:88) at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:87) at java.sql.DriverManager.getConnection(DriverManager.java:620) at java.sql.DriverManager.getConnection(DriverManager.java:200) at JDBCClient.getDriverConnection(JDBCClient.java:53) at JDBCClient.main(JDBCClient.java:41) Caused by: [LogonException]Remote org.teiid.client.security.LogonException: VDB "barfingToad" version "latest" is not in "active" status. 1 [TeiidSecurityException]Remote org.teiid.dqp.service.SessionServiceException: VDB "barfingToad" version "latest" is not in "active" status. at org.teiid.transport.LogonImpl.logon(LogonImpl.java:84) at sun.reflect.GeneratedMethodAccessor1087.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:189) at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160) at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149) at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: [TeiidSecurityException]Remote org.teiid.dqp.service.SessionServiceException: VDB "barfingToad" version "latest" is not in "active" status. at org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:225) at org.teiid.services.SessionServiceImpl.createSession(SessionServiceImpl.java:157) at org.teiid.transport.LogonImpl.logon(LogonImpl.java:75) ... 31 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010