September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2424) Create OSGi bundles for Embedded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2424?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2424. --------------------------------- Labels: Alpha1 (was: ) Fix Version/s: (was: Open To Community) Resolution: Done Changed the build such that all relevant Teiid jar files are built as OSGI bundles. These bundles can be used to deploy Teiid jars into OSGI containers like eclipse osgi or karaf/felix. Also provided a starter features.xml file for Karaf container, that adds all the Teiid jars and its dependencies. There were some translators are not added to this file due to failure to define transitive dependencies without them being a OSGI bundles. For example you can deploy in karaf like below {code} features:addurl mvn:org.jboss.teiid/teiid/8.6.0.Alpha1-SNAPSHOT/xml/karaf-features features:install -v teiid {code} Note that the above just installs JAR files into container, akin specifying a classpath on Java program, if one wants to have true working Teiid system on the Karaf, they need to write module that simply does a what an "embedded" kit example is doing. If is really motivated, they can even write a alternative to "jboss-as" runtime system using this, if you can pull all the other necessary pieces like transactions, deployers, jaas, configuration etc under this container. > Create OSGi bundles for Embedded > -------------------------------- > > Key: TEIID-2424 > URL: https://issues.jboss.org/browse/TEIID-2424 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi, Embedded > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.6 > > > Embedded should be available as an OSGi bundle(s). It may also be useful for Designer to consume us through bundles as well. -- 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-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 commented on TEIID-2668: --------------------------------------- Did you retest with a later client or on a later version entirely? > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2439) jdbc socket transport support in teiid embedded mode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2439?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2439: ---------------------------------- Assignee: Ramesh Reddy > jdbc socket transport support in teiid embedded mode > ---------------------------------------------------- > > Key: TEIID-2439 > URL: https://issues.jboss.org/browse/TEIID-2439 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Reporter: Himanshu Kapoor > Assignee: Ramesh Reddy > Fix For: 8.6 > > > As a teiid embedded user there must be JDBC socket transport in embedded mode so that external java application (outside the application server in which teiid embedded has been hosted) can connect to the vdb's using the teiid jdbc driver and can perform operation on it. > This feature will really help the teiid embedded users to start using this feature in enterprises level applications . -- 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-2669) In subquery with no values returns wrong result

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2669. ----------------------------------- Resolution: Done Our consideration of three-value null handling for the left expression was trumping the proper handling of empty in/quantified comparison. Corrected the rewriter and evaluator. > In subquery with no values returns wrong result > ----------------------------------------------- > > Key: TEIID-2669 > URL: https://issues.jboss.org/browse/TEIID-2669 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.6 > > > If an in subquery is entered such that no rows will be returned and it is not pushed down, then the rewriter will incorrectly convert the in predicate to an is not null check. -- 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-2669) In subquery with no values returns wrong result

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2669: ---------------------------------- Priority: Blocker (was: Critical) > In subquery with no values returns wrong result > ----------------------------------------------- > > Key: TEIID-2669 > URL: https://issues.jboss.org/browse/TEIID-2669 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.6 > > > If an in subquery is entered such that no rows will be returned and it is not pushed down, then the rewriter will incorrectly convert the in predicate to an is not null check. -- 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-2669) In subquery with no values returns wrong result

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2669: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1010344|https://bugzilla.redhat.com/show_bug.cgi?id=1010344] from NEW to ASSIGNED > In subquery with no values returns wrong result > ----------------------------------------------- > > Key: TEIID-2669 > URL: https://issues.jboss.org/browse/TEIID-2669 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.6 > > > If an in subquery is entered such that no rows will be returned and it is not pushed down, then the rewriter will incorrectly convert the in predicate to an is not null check. -- 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-2669) In subquery with no values returns wrong result

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2669: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1010318, https://bugzilla.redhat.com/show_bug.cgi?id=1010344 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1010318) > In subquery with no values returns wrong result > ----------------------------------------------- > > Key: TEIID-2669 > URL: https://issues.jboss.org/browse/TEIID-2669 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.6 > > > If an in subquery is entered such that no rows will be returned and it is not pushed down, then the rewriter will incorrectly convert the in predicate to an is not null check. -- 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-2669) In subquery with no values returns wrong result

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2669: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1010318 > In subquery with no values returns wrong result > ----------------------------------------------- > > Key: TEIID-2669 > URL: https://issues.jboss.org/browse/TEIID-2669 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.6 > > > If an in subquery is entered such that no rows will be returned and it is not pushed down, then the rewriter will incorrectly convert the in predicate to an is not null check. -- 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-2669) In subquery with no values returns wrong result

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2669: ------------------------------------- Summary: In subquery with no values returns wrong result Key: TEIID-2669 URL: https://issues.jboss.org/browse/TEIID-2669 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.6 If an in subquery is entered such that no rows will be returned and it is not pushed down, then the rewriter will incorrectly convert the in predicate to an is not null check. -- 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-2666) Extend OData output formats, currently JSON and XML supported

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2666: --------------------------------------- As Ramesh say this would require odata4j to support extensible formats since they are unlikely to add direct support for csv - which from the odata mailing lists there is resistance toward considering in general given the lack of metadata and lack of a standard way to represent hierarchical data. Assuming xml/atom and applying xslt on top while conceptually simple would still require an odata4j extension - and would require even more changes on their side as the format strings would not be fixed. So for us to pursue this it would have to be pretty high value as we'd likely end up with temporary (or permanent) patches against odata4j. > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4 > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Steven Hawkins > Priority: Trivial > > We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request. > It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013