October 2013 - teiid-issues - Jboss List Archives

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

by Jing Li (JIRA)

[ https://issues.jboss.org/browse/TEIID-2668?page=com.atlassian.jira.plugin... ] Jing Li commented on TEIID-2668: -------------------------------- Steven, We retested with Teiid 8.4 client (server side is still 8.3), still got same errors. Where is your fix for this issue? Upgrade client side is good enough? For now, we can't upgrade our server side to Teiid 8.4. Thank you, Jing > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2679) future proof the client handshake client/server version

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2679?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2679: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1015235|https://bugzilla.redhat.com/show_bug.cgi?id=1015235] from ASSIGNED to MODIFIED > future proof the client handshake client/server version > ------------------------------------------------------- > > Key: TEIID-2679 > URL: https://issues.jboss.org/browse/TEIID-2679 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver, Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > Until the version logic in the DQPWorkContext, the version strings are being compared lexically which will have an issue with any version part greater than 9. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2665: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1016111 > Hive translator pushdown improvements > ------------------------------------- > > Key: TEIID-2665 > URL: https://issues.jboss.org/browse/TEIID-2665 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.6 > > > - Hive 0.11 windowing functions: push down > - Native Queries support > - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table > - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2689) support for pg regproc cast

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2689: ------------------------------------- Summary: support for pg regproc cast Key: TEIID-2689 URL: https://issues.jboss.org/browse/TEIID-2689 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 8.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.6 Attempting to use the PG 8.3 JDBC driver against an 8.6/master instance, a query against pg_proc (select * from pg_proc) failed due to how the older driver was looking up additional metadata with our enhanced support for array types - this does not occur in a 7.7 Teiid. The offending query will complete as expected with support for the ::regproc cast. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2665: ------------------------------------- Ok, I was trying to push a "source" defined aggregate UDF. So, I am not sure how that can be accomplished. Please go ahead fix as you see. > Hive translator pushdown improvements > ------------------------------------- > > Key: TEIID-2665 > URL: https://issues.jboss.org/browse/TEIID-2665 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.6 > > > - Hive 0.11 windowing functions: push down > - Native Queries support > - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table > - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2665: --------------------------------------- I mean the changes specifically to the userdefined aggregatefunction. At that point you are going to be processed in the engine. All pushdown decisions have been. > Hive translator pushdown improvements > ------------------------------------- > > Key: TEIID-2665 > URL: https://issues.jboss.org/browse/TEIID-2665 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.6 > > > - Hive 0.11 windowing functions: push down > - Native Queries support > - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table > - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2665: ------------------------------------- without those additions I could not push the aggregates to push to source, which were supported by the source > Hive translator pushdown improvements > ------------------------------------- > > Key: TEIID-2665 > URL: https://issues.jboss.org/browse/TEIID-2665 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.6 > > > - Hive 0.11 windowing functions: push down > - Native Queries support > - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table > - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2687?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2687: ------------------------------------- Some of the translator names are same as the resource-adapter names so that may have worked. What I mean we need to generally get away from connector semantics, Teiid still have many references to connectors > Expose Translator override property definitions through Admin API > ----------------------------------------------------------------- > > Key: TEIID-2687 > URL: https://issues.jboss.org/browse/TEIID-2687 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > > Currently in the admin api > {code} > public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException; > {code} > only works with resource-adapters and data sources in terms of returning the properties that can be configured on them. > This request is to extend the functionality to return the "overridable" properties for "translators", such as > {code} > public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException; > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2665: --------------------------------------- What is the purpose of the changes in UserDefined? It doesn't seem like that level of processing should be concerned with pushdown. > Hive translator pushdown improvements > ------------------------------------- > > Key: TEIID-2665 > URL: https://issues.jboss.org/browse/TEIID-2665 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.6 > > > - Hive 0.11 windowing functions: push down > - Native Queries support > - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table > - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2688) NPE determining dependent join cost

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2688?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2688: ---------------------------------- Fix Version/s: 7.7.8 > NPE determining dependent join cost > ----------------------------------- > > Key: TEIID-2688 > URL: https://issues.jboss.org/browse/TEIID-2688 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 7.7.8 > > > Given that the initial node in the cost determination is not a select node if it is "pushed" to a point where the criteria is assumed to exist, then an NPE is thrown: > java.lang.NullPointerException > at org.teiid.query.optimizer.relational.rules.JoinUtil.replaceWithNullValues(JoinUtil.java:186) > at org.teiid.query.optimizer.relational.rules.JoinUtil.isNullDependent(JoinUtil.java:141) > at org.teiid.query.optimizer.relational.rules.JoinUtil.optimizeJoinType(JoinUtil.java:106) > at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.examinePath(RulePushSelectCriteria.java:356) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.determineTargets(NewCalculateCostUtil.java:1294) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForDepJoin(NewCalculateCostUtil.java:1155) > at org.teiid.query.optimizer.relational.rules.JoinRegion.getDepJoinCost(JoinRegion.java:373) > at org.teiid.query.optimizer.relational.rules.JoinRegion.scoreRegion(JoinRegion.java:316) > at org.teiid.query.optimizer.relational.rules.RulePlanJoins.findBestJoinOrder(RulePlanJoins.java:571) > at org.teiid.query.optimizer.relational.rules.RulePlanJoins.execute(RulePlanJoins.java:173) > at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:525) > at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:212) > at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:195) > This will occur if the prospective dependent join for example is above an outer join such that we need to check whether pushing the criteria would alter the meaning of the join. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2013