February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2830) One-2-One mapping in MongoDB should not require PK on child table

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2830?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2830: -------------------------------- Summary: One-2-One mapping in MongoDB should not require PK on child table (was: One-2-One mappiing in MongoDB should not require PK on child table) > One-2-One mapping in MongoDB should not require PK on child table > ----------------------------------------------------------------- > > Key: TEIID-2830 > URL: https://issues.jboss.org/browse/TEIID-2830 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7 > > > A schema like > {code} > CREATE FOREIGN TABLE Customer ( > CustomerId integer PRIMARY KEY, > FirstName varchar(25), > LastName varchar(25), > ) OPTIONS(UPDATABLE 'TRUE'); > > CREATE FOREIGN TABLE Address ( > CustomerId integer, > Street varchar(50), > City varchar(25), > State varchar(25), > Zipcode varchar(6), > FOREIGN KEY (CustomerId) REFERENCES Customer (CustomerId), > ) OPTIONS(UPDATABLE 'TRUE', teiid_mongo:MERGE 'Customer'); > {code} > will fail on second insert with NPE for lack of PK on the Address table > {code} > insert into Customer (customer_id ,first_name,last_name) values ('1002','Syed','Iqbal'); > insert into Address (customer_id,street,city,state,zipcode) values ('1002','123 Main St','Chicago','IL','60659'); > {code} > the Exception is > {code} > 09:38:53,250 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue11) 70p5084MEtHx Connector worker process failed for atomic-request=70p5084MEtHx.0.0.3: java.lang.NullPointerException > at org.teiid.translator.mongodb.MongoDocument.buildMergeKey(MongoDocument.java:252) > at org.teiid.translator.mongodb.MongoDocument.build(MongoDocument.java:143) > at org.teiid.translator.mongodb.MongoDocument.<init>(MongoDocument.java:64) > at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:400) > at org.teiid.language.NamedTable.acceptVisitor(NamedTable.java:66) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT] > at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:95) > at org.teiid.translator.mongodb.MongoDBUpdateVisitor.visit(MongoDBUpdateVisitor.java:59) > at org.teiid.language.Insert.acceptVisitor(Insert.java:57) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT] > {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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2837: -------------------------------- Summary: Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name Key: TEIID-2837 URL: https://issues.jboss.org/browse/TEIID-2837 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.6 Environment: Cassandra with Teiid 8.6 Reporter: Ivan Chan Assignee: Steven Hawkins Teiid doesn't work with KeySpace or Table which contains UpperCase. Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table: http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE Exception when try to deploy: java.lang.NullPointerException at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52) at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100) at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644) at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161) at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605) at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536) -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2035: ------------------------------------------------ Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 985578|https://bugzilla.redhat.com/show_bug.cgi?id=985578] from ON_QA to VERIFIED > DeleteDataSource method on Admin API does not completely delete the Connection Factory > -------------------------------------------------------------------------------------- > > Key: TEIID-2035 > URL: https://issues.jboss.org/browse/TEIID-2035 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.4.1, 8.5 > > > ConnectionFactory requires a two step creation process > 1) create the resource-adaptor section > 2) connection factory section > The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2836) Retreived records less than actual when data is stored in EBCDIC

by Van Halbert (JIRA)

Van Halbert created TEIID-2836: ---------------------------------- Summary: Retreived records less than actual when data is stored in EBCDIC Key: TEIID-2836 URL: https://issues.jboss.org/browse/TEIID-2836 Project: Teiid Issue Type: Bug Reporter: Van Halbert Assignee: Steven Hawkins One of views in my vdb joins a table in DB2 on z/OS which has EBCDIC data with other table in Oracle which has SJIS data. It returns records less than actual. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2836) Retreived records less than actual when data is stored in EBCDIC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2836?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2836: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060951 > Retreived records less than actual when data is stored in EBCDIC > ---------------------------------------------------------------- > > Key: TEIID-2836 > URL: https://issues.jboss.org/browse/TEIID-2836 > Project: Teiid > Issue Type: Bug > Reporter: Van Halbert > Assignee: Steven Hawkins > > One of views in my vdb joins a table in DB2 on z/OS which has EBCDIC data with other table in Oracle which has SJIS data. It returns records less than actual. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2835: --------------------------------------- This exception should only occur after 10 failed handshakes. If your machine wasn't under heavy load, having network issues, etc. then this is not expected. > After switch to use io.netty, getting exception in TestJDBCSocketTransport > -------------------------------------------------------------------------- > > Key: TEIID-2835 > URL: https://issues.jboss.org/browse/TEIID-2835 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: Running build on mac > Reporter: Van Halbert > Assignee: Steven Hawkins > > When building off of master (which I see there's been a change to io.netty), I get the following error: > Running org.teiid.transport.TestJDBCSocketTransport > Feb 3, 2014 2:51:12 PM org.teiid.logging.JavaLogger log > SEVERE: TEIID40113 Unhandled exception, aborting operation > org.jboss.netty.handler.codec.frame.TooLongFrameException: Adjusted frame length exceeds 100000: 100293 - discarded > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:417) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:405) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:320) > at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:108) > at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) > at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > I made a change to SSLAwareChannelHandler to increase the estimated decoder size to Integer.MAX_VALUE and the problem was gone. Here's the difference in size estimates based on what the default was using and the MAX_VALUE I tested with: > =========== DEFAULT ===========2097152 > =========== Int Max ===========2147483647 -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2825) Add module packaging to each of the translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2825?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-2825. -------------------------------- Resolution: Done Steve made the changes to include the correct dependencies in the module-dist.zip. > Add module packaging to each of the translator > ---------------------------------------------- > > Key: TEIID-2825 > URL: https://issues.jboss.org/browse/TEIID-2825 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Add zip module packaging to each of the translators -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2835: ------------------------------------ I thought that was the issue, but it ends with a time out issue, that appears, probably, to be mac related. Feb 3, 2014 4:10:54 PM org.teiid.net.socket.SocketServerConnectionFactory$1 run WARNING: Error performing keep-alive ping java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.DataInputStream.readInt(DataInputStream.java:370) at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:97) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:343) at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:109) at org.teiid.net.socket.SocketServerInstanceImpl.doHandshake(SocketServerInstanceImpl.java:116) at org.teiid.net.socket.SocketServerInstanceImpl.connect(SocketServerInstanceImpl.java:96) at org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance(SocketServerConnectionFactory.java:271) at org.teiid.net.socket.SocketServerConnectionFactory$1.run(SocketServerConnectionFactory.java:201) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Feb 3, 2014 4:10:55 PM org.teiid.logging.JavaLogger log WARNING: TEIID40114 Unhandled exception, closing client instance: Connection reset by peer > After switch to use io.netty, getting exception in TestJDBCSocketTransport > -------------------------------------------------------------------------- > > Key: TEIID-2835 > URL: https://issues.jboss.org/browse/TEIID-2835 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: Running build on mac > Reporter: Van Halbert > Assignee: Steven Hawkins > > When building off of master (which I see there's been a change to io.netty), I get the following error: > Running org.teiid.transport.TestJDBCSocketTransport > Feb 3, 2014 2:51:12 PM org.teiid.logging.JavaLogger log > SEVERE: TEIID40113 Unhandled exception, aborting operation > org.jboss.netty.handler.codec.frame.TooLongFrameException: Adjusted frame length exceeds 100000: 100293 - discarded > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:417) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:405) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:320) > at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:108) > at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) > at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > I made a change to SSLAwareChannelHandler to increase the estimated decoder size to Integer.MAX_VALUE and the problem was gone. Here's the difference in size estimates based on what the default was using and the MAX_VALUE I tested with: > =========== DEFAULT ===========2097152 > =========== Int Max ===========2147483647 -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2763) kerberosServicePrincipleName as user when dealing with kerberos security domain

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2763?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2763. --------------------------------- Resolution: Done In the case of Kerberoes based authntication and no "user" information is supplied on the JDBC URL then "kerberosServicePrincipleName" proeprty value will be used as the user name. Previously the documentation was written such that, it was forcing a second authentication on Teiid layer using a simple user name/passwd on top of the kerberoes. Which is not really needed. It will only designed for assigning a generic user to the kerberos authenticated user and add any role information. As part of this JIRA, I also added a SimpleLoginModule, which works as pass-through based on just name (kerberosServicePrincipleName) and null password. Thus, only Kerberoes is real authentication. This login-module can be stacked to supply the role information, and example is shown in the documentation. https://docs.jboss.org/author/display/TEIID/Kerberos+support+through+GSSAPI > kerberosServicePrincipleName as user when dealing with kerberos security domain > ------------------------------------------------------------------------------- > > Key: TEIID-2763 > URL: https://issues.jboss.org/browse/TEIID-2763 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.6 > Environment: Windows 2008R2 > Reporter: Andy Yip > Assignee: Ramesh Reddy > Labels: authentication, login-module > Fix For: 8.7 > > > When both the security-domain and krb5-domain is defined within the transport authentication element. The security-domain module does not take into account of kerberosServicePrincipleName. This means a username (and/or password) is still required in the connection url forthe security-domain's authentication/authorization. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2712: ------------------------------------------------ Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1023216|https://bugzilla.redhat.com/show_bug.cgi?id=1023216] from ON_QA to ASSIGNED > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014