September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2667) Keys are not imported by default when using dynamic VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2667?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2667: ---------------------------------- Fix Version/s: 8.4.1 Affects Version/s: 7.7 (was: 8.4.1) > Keys are not imported by default when using dynamic VDB > ------------------------------------------------------- > > Key: TEIID-2667 > URL: https://issues.jboss.org/browse/TEIID-2667 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Server > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > Primary and foreign keys are not imported by defaut when using dynamic VDB. > According to the documentation they should be imported by default when using JDBC translator. -- 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-1979) The RAR should be unbundled when packaged in the jboss kit

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1979?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-1979: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 868964|https://bugzilla.redhat.com/show_bug.cgi?id=868964] I assume this issue does not need to be documented in the Release Notes - setting to requires_doc_text- accordingly. > The RAR should be unbundled when packaged in the jboss kit > ---------------------------------------------------------- > > Key: TEIID-1979 > URL: https://issues.jboss.org/browse/TEIID-1979 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.4 > > > The RAR file should be unbundled, instead of zipped up, when it is packaged in the jboss kit. This change is being pushed up stream. -- 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-2667) Keys are not imported by default when using dynamic VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2667?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2667: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1009460|https://bugzilla.redhat.com/show_bug.cgi?id=1009460] from NEW to ASSIGNED > Keys are not imported by default when using dynamic VDB > ------------------------------------------------------- > > Key: TEIID-2667 > URL: https://issues.jboss.org/browse/TEIID-2667 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.6 > > > Primary and foreign keys are not imported by defaut when using dynamic VDB. > According to the documentation they should be imported by default when using JDBC translator. -- 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-2667) Keys are not imported by default when using dynamic VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2667?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2667. ----------------------------------- Fix Version/s: 8.6 Resolution: Done Resolved for 8.6. Let me know when it can be committed to 8.4.x > Keys are not imported by default when using dynamic VDB > ------------------------------------------------------- > > Key: TEIID-2667 > URL: https://issues.jboss.org/browse/TEIID-2667 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.6 > > > Primary and foreign keys are not imported by defaut when using dynamic VDB. > According to the documentation they should be imported by default when using JDBC translator. -- 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: --------------------------------------- More than likely this is TEIID-2505 can you retest using the 8.4 or 8.5 client? > 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-2668) Teiid procedure input parameter has limit for bulk data

by Jing Li (JIRA)

Jing Li created TEIID-2668: ------------------------------ Summary: 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-2424) Create OSGi bundles for Embedded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2424?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2424: ----------------------------------- Assignee: Ramesh Reddy > 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 > Fix For: 8.6, Open To Community > > > 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-2667) Keys are not imported by default when using dynamic VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2667?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2667: --------------------------------------- It looks like several of the documented properties do not match the defaults: importIndexes, importKeys, importProcedures and autoCreateUniqueConstraints is also missing from the doc page (added with TEIID-1946 and roughly corresponds to the designer option to import incomplete foreign keys). I believe we at one point were trying to mimic Designer's defaults as much as it made sense. At least having importProcedures/importIndexes defaulted as false is fine, so the doc should be changed for those. Since we don't split importKeys into primary/unique vs. foreign, having it defaulted to false doesn't make much sense. As long as autoCreateUniqueConstraints is true (the default) and given that we automatically ignore foreign keys to non-imported tables, then there's no chance that having importKeys set to true should result in invalid metadata. We would just want to document the switch in the actual default as a compatibility change if for whatever reason someone was relying on the current behavior. > Keys are not imported by default when using dynamic VDB > ------------------------------------------------------- > > Key: TEIID-2667 > URL: https://issues.jboss.org/browse/TEIID-2667 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Primary and foreign keys are not imported by defaut when using dynamic VDB. > According to the documentation they should be imported by default when using JDBC translator. -- 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-2667) Keys are not imported by default when using dynamic VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2667?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2667: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1009460 > Keys are not imported by default when using dynamic VDB > ------------------------------------------------------- > > Key: TEIID-2667 > URL: https://issues.jboss.org/browse/TEIID-2667 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Primary and foreign keys are not imported by defaut when using dynamic VDB. > According to the documentation they should be imported by default when using JDBC translator. -- 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-2667) Keys are not imported by default when using dynamic VDB

by Van Halbert (JIRA)

Van Halbert created TEIID-2667: ---------------------------------- Summary: Keys are not imported by default when using dynamic VDB Key: TEIID-2667 URL: https://issues.jboss.org/browse/TEIID-2667 Project: Teiid Issue Type: Bug Components: JDBC Connector, Server Affects Versions: 8.4.1 Reporter: Van Halbert Assignee: Steven Hawkins Primary and foreign keys are not imported by defaut when using dynamic VDB. According to the documentation they should be imported by default when using JDBC translator. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013