September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2669) In subquery with no values returns wrong result

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-2669: -------------------------------- > 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 Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2669?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2669: ------------------------------- Fix Version/s: 8.4.1 > 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.4.1, 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-2659) A domain member server cannot list translators

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2659?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2659. --------------------------------- Resolution: Won't Fix > A domain member server cannot list translators > ---------------------------------------------- > > Key: TEIID-2659 > URL: https://issues.jboss.org/browse/TEIID-2659 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > Using the teiid client and calling 'admin.getTranslators()' fails to return any translators on a domain-member server. (this partially succeeds on the domain master) > The request does not throw an exception but its outcome fails with the following result: > {code} > "outcome" => "failed", > "failure-description" => "JBAS010849: Operation list-translators for address [ > (\"profile\" => \"ha\"), > (\"subsystem\" => \"teiid\") > ] can only be handled by the master Domain Controller; this host is not the master Domain Controller", > "rolled-back" => true > {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, 3 months

1
0
0 / 0

[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 will migrate to 8.4 soon, after we migrate, we will test it and let you know. Thanks for following up. 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2659) A domain member server cannot list translators

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIID-2659?page=com.atlassian.jira.plugin... ] Paul Richardson commented on TEIID-2659: ---------------------------------------- I do agree. JBT does not support domain mode explicitly and until their use cased are functionally fleshed out then I don't see an alternative. > A domain member server cannot list translators > ---------------------------------------------- > > Key: TEIID-2659 > URL: https://issues.jboss.org/browse/TEIID-2659 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > Using the teiid client and calling 'admin.getTranslators()' fails to return any translators on a domain-member server. (this partially succeeds on the domain master) > The request does not throw an exception but its outcome fails with the following result: > {code} > "outcome" => "failed", > "failure-description" => "JBAS010849: Operation list-translators for address [ > (\"profile\" => \"ha\"), > (\"subsystem\" => \"teiid\") > ] can only be handled by the master Domain Controller; this host is not the master Domain Controller", > "rolled-back" => true > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2670) VDB connection type(Any, none, Version_specific) are not persisted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2670?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2670: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1010417|https://bugzilla.redhat.com/show_bug.cgi?id=1010417] from NEW to ASSIGNED > VDB connection type(Any,none,Version_specific) are not persisted > ---------------------------------------------------------------- > > Key: TEIID-2670 > URL: https://issues.jboss.org/browse/TEIID-2670 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.4.1, 8.6 > > > The connection type attribute in VDB is not being persistent across server re-loads. If user changes from default "BY_VERSION" to another value, after the restart of the server the value is being reset to "BY_VERSION". > Lack of this persistence makes the VDB version rolling and working with multiple versions of VDB not possible with server restarts. -- 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-2670) VDB connection type(Any, none, Version_specific) are not persisted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2670?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2670: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1010417 > VDB connection type(Any,none,Version_specific) are not persisted > ---------------------------------------------------------------- > > Key: TEIID-2670 > URL: https://issues.jboss.org/browse/TEIID-2670 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.4.1, 8.6 > > > The connection type attribute in VDB is not being persistent across server re-loads. If user changes from default "BY_VERSION" to another value, after the restart of the server the value is being reset to "BY_VERSION". > Lack of this persistence makes the VDB version rolling and working with multiple versions of VDB not possible with server restarts. -- 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-2670) VDB connection type(Any, none, Version_specific) are not persisted

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2670?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2670: ------------------------------------- The "connection-type" has never been added to the vdb.xml schema or to persistence classes. It was only captured in the VDBMetadata class, thus during the restarts of the server reverting to default value. This has been fixed on 8.6 master branch now. > VDB connection type(Any,none,Version_specific) are not persisted > ---------------------------------------------------------------- > > Key: TEIID-2670 > URL: https://issues.jboss.org/browse/TEIID-2670 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.4.1, 8.6 > > > The connection type attribute in VDB is not being persistent across server re-loads. If user changes from default "BY_VERSION" to another value, after the restart of the server the value is being reset to "BY_VERSION". > Lack of this persistence makes the VDB version rolling and working with multiple versions of VDB not possible with server restarts. -- 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-2659) A domain member server cannot list translators

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2659?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2659: --------------------------------------- Paul do you agree with Ramesh, or does something need to be raised with Brian? > A domain member server cannot list translators > ---------------------------------------------- > > Key: TEIID-2659 > URL: https://issues.jboss.org/browse/TEIID-2659 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > Using the teiid client and calling 'admin.getTranslators()' fails to return any translators on a domain-member server. (this partially succeeds on the domain master) > The request does not throw an exception but its outcome fails with the following result: > {code} > "outcome" => "failed", > "failure-description" => "JBAS010849: Operation list-translators for address [ > (\"profile\" => \"ha\"), > (\"subsystem\" => \"teiid\") > ] can only be handled by the master Domain Controller; this host is not the master Domain Controller", > "rolled-back" => true > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2670) VDB connection type(Any, none, Version_specific) are not persisted

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2670: ----------------------------------- Summary: VDB connection type(Any,none,Version_specific) are not persisted Key: TEIID-2670 URL: https://issues.jboss.org/browse/TEIID-2670 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 8.4.1, 8.6 The connection type attribute in VDB is not being persistent across server re-loads. If user changes from default "BY_VERSION" to another value, after the restart of the server the value is being reset to "BY_VERSION". Lack of this persistence makes the VDB version rolling and working with multiple versions of VDB not possible with server restarts. -- 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