December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2757: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1044072 > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: List of invalid XML characters.docx, TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2779) Configurable CommonTableExpression support for DB2

by Andriy Rokhmanov (JIRA)

Andriy Rokhmanov created TEIID-2779: --------------------------------------- Summary: Configurable CommonTableExpression support for DB2 Key: TEIID-2779 URL: https://issues.jboss.org/browse/TEIID-2779 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 8.5 Reporter: Andriy Rokhmanov Assignee: Steven Hawkins The LIMIT clause (FETCH FIRST...) inside CTE (WITH...) is not supported on pre-V9 versions of DB2 on z/OS, or new versions of DB2 running in Compatibility Mode. The CTE support in DB2 translator should be configurable. See more information: https://community.jboss.org/thread/235503 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2668) Teiid procedure input parameter has limit for bulk data

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2668?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2668. ----------------------------------- Resolution: Duplicate Issue Resolving as a duplicate of TEIID-2750. There is now a system property on the server side to adjust the max message size and the default was increased from 1 to 2 megs. > Teiid procedure input parameter has limit for bulk data > ------------------------------------------------------- > > Key: TEIID-2668 > URL: https://issues.jboss.org/browse/TEIID-2668 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.3 > Environment: Teiid 8.3. > Reporter: Jing Li > Assignee: Steven Hawkins > > We wrote a Teiid procedure, one of the input parameters is List<List<Double>>. We found if we give too many data in there, e.g. 200x375, Teiid will throw out exception before go to my translator: > org.teiid.jdbc.TeiidSQLException: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Connection reset by peer: socket write error > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:113) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:70) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:631) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:559) > at org.teiid.jdbc.PreparedStatementImpl.execute(PreparedStatementImpl.java:201) > at MyTest.testHorizon3DWrite(MyTest.java:102) > at MyTest.main(MyTest.java:27) > Caused by: [TeiidComponentException] TEIID20013: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Connection reset by peer: socket write error > 1 [SingleInstanceCommunicationException] TEIID20013: Error Code:TEIID20013 Message:java.net.SocketException: Connection reset by peer: socket write error > 2 [ExecutionException]java.net.SocketException: Connection reset by peer: socket write error > 3 [SocketException]Connection reset by peer: socket write error > at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:61) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:374) > at org.teiid.net.socket.SocketServerConnection$1.invoke(SocketServerConnection.java:243) > at $Proxy7.executeRequest(Unknown Source) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:629) > ... 4 more > Caused by: [SingleInstanceCommunicationException] TEIID20013: Error Code:TEIID20013 Message:java.net.SocketException: Connection reset by peer: socket write error > 1 [ExecutionException]java.net.SocketException: Connection reset by peer: socket write error > 2 [SocketException]Connection reset by peer: socket write error > at org.teiid.net.socket.SocketServerInstanceImpl.send(SocketServerInstanceImpl.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:102) > at $Proxy1.send(Unknown Source) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:362) > ... 7 more > Caused by: java.util.concurrent.ExecutionException: java.net.SocketException: Connection reset by peer: socket write error > at org.teiid.client.util.ResultsFuture.convertResult(ResultsFuture.java:100) > at org.teiid.client.util.ResultsFuture.get(ResultsFuture.java:95) > at org.teiid.net.socket.SocketServerInstanceImpl.send(SocketServerInstanceImpl.java:174) > ... 14 more > Caused by: java.net.SocketException: Connection reset by peer: socket write error > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) > at java.io.DataOutputStream.write(DataOutputStream.java:90) > at org.teiid.netty.handler.codec.serialization.ObjectEncoderOutputStream.writeObjectOverride(ObjectEncoderOutputStream.java:65) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) > at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.write(OioOjbectChannelFactory.java:130) > at org.teiid.net.socket.SocketServerInstanceImpl.send(SocketServerInstanceImpl.java:173) > ... 14 more > But if we give less number of data in that param, e.g. 100x375, it works fine. > Thanks. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2661) Mistakenly replanning on subsequent executions of continuous execution

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2661?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2661. --------------------------------- > Mistakenly replanning on subsequent executions of continuous execution > ---------------------------------------------------------------------- > > Key: TEIID-2661 > URL: https://issues.jboss.org/browse/TEIID-2661 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.5 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.6 > > > The first time through we are mistakenly replanning the execution during continuous executions. > See https://community.jboss.org/thread/232434 for more detail -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2674) Makedep not honored with aggregate decomposition

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2674?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2674. --------------------------------- > Makedep not honored with aggregate decomposition > ------------------------------------------------ > > Key: TEIID-2674 > URL: https://issues.jboss.org/browse/TEIID-2674 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > A makedep hint on a joined table under aggregation for a source that does not support the grouping will result in the makedep hint being ignored - for example where pm1 does not support join/aggregation: > select count(x.e2), e1 from pm1.g1 x makedep, pm1.g2 where x.e3 = pm1.g2.e3 group by e1 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2693) Logging/message tweaks

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2693?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2693. --------------------------------- > Logging/message tweaks > ---------------------- > > Key: TEIID-2693 > URL: https://issues.jboss.org/browse/TEIID-2693 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > The source sql is being redundantly logged in JDBCQueryExecution. > We should continue to refine how odbc/jdbc uncaught exceptions are logged - if it's not clearly a closed connection, then it should be a warning. > If a local connection is tried outside of AS the result is an npe. A better message should be given. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2680) VDBService not properly detecting missing delegate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2680?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2680. --------------------------------- > VDBService not properly detecting missing delegate > -------------------------------------------------- > > Key: TEIID-2680 > URL: https://issues.jboss.org/browse/TEIID-2680 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1, 8.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > This is a regression introduced by TEIID-2629. The getExecutionFactory check for setting the delegate is incorrect. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2344) Determine database version automatically

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2344?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2344. --------------------------------- > Determine database version automatically > ---------------------------------------- > > Key: TEIID-2344 > URL: https://issues.jboss.org/browse/TEIID-2344 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > It would be helpful if we could determine the database version automatically from the database metadata rather than relying on the user setting. Of course if the property setting is present we shouldn't override it. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2685) Add SAP Netweaver translator based on OData

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2685?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2685. --------------------------------- > Add SAP Netweaver translator based on OData > ------------------------------------------- > > Key: TEIID-2685 > URL: https://issues.jboss.org/browse/TEIID-2685 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > Based on http://scn.sap.com/docs/DOC-44986 document, the SAP net weaver gateway's metadata is enhanced by SAP, that does not behave as expected by the complete OData spec. > Teiid needs to introduce a new translator called "sap-nw" based on OData that take these SAP specific metadata into account -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-669) Support "pass though" SQL commands to sources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-669?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-669. -------------------------------- > Support "pass though" SQL commands to sources > --------------------------------------------- > > Key: TEIID-669 > URL: https://issues.jboss.org/browse/TEIID-669 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.2 > > > Currently there is no mechanism in Teiid, when a query is submitted to a runtime engine that is passed through the query engine unadulterated and unmodified and submitted directly to a source connector. All queries are parsed, optimized, re-written. Some times this limits the functionality in Teiid, when a user would like to execute a query that is very "source" specific. For example Oracle supports lots of Oracle specific functions that are not supported by the SQL spec, to support execution of these in Teiid user need to resort to UDF, which is cumbersome and involves modelling. > Another benefit of this is also to pass DDL to sources, currently since Teiid does not support DDL, this is not possible at all. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013