March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3005: ------------------------------------ Is there anything left do here? > Support Kerberos pass-thru to the data source > --------------------------------------------- > > Key: TEIID-3005 > URL: https://issues.jboss.org/browse/TEIID-3005 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution. > This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3005: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Support Kerberos pass-thru to the data source > --------------------------------------------- > > Key: TEIID-3005 > URL: https://issues.jboss.org/browse/TEIID-3005 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution. > This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4064) OData - missing non-nullable property

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4064?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4064. --------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done Labels: Alpha3 (was: ) The issue with JIRA is code was not accounting for the null results that come from the Left outer join of the query in the case of $expand. Corrected the code to check the key values of the entity before sending them to serialization. Thus creating the correct response. > OData - missing non-nullable property > ------------------------------------- > > Key: TEIID-4064 > URL: https://issues.jboss.org/browse/TEIID-4064 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > Change DDL for tables Customer and Orders in VDB as follows: > {code:sql} > CREATE FOREIGN TABLE Customers ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS'); > CREATE FOREIGN TABLE Orders ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > customerid integer, > place varchar(10), > FOREIGN KEY (customerid) REFERENCES Customers(id)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS'); > {code} > Note, that both tables have same name of primary key named "id". > Invoke GET method to URL http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Result:* > {code:xml} > <error> > <code>400</code> > <message>The non-nullable property 'id' is missing.</message> > </error> > {code} > Here are selected part of Teiid's log: > *Query:* > {code:sql} > SELECT g10.id, g10.name, g11.id, g11.customerid, g11.place FROM Source.Customers AS g10 LEFT OUTER JOIN Source.Orders AS g11 ON g10.id = g11.customerid ORDER BY g10.id > {code} > *Result:* > |id|name|id|customerid|place| > |1|customer1|1|1|town| > |1|customer1|2|1|state| > |1|customer1|3|1|country| > |1|customer1|4|1|abroad| > |2|customer2|5|2|state| > |2|customer2|6|2|country| > |3|customer3|7|3|town| > |3|customer3|8|3|town| > |4|customer4|<null>|<null>|<null>| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4045) OData throws unknown error if $select is applied to expanded entity

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4045?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4045. --------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done Implicitly added the keys for the $expand entity to the query such that the ID of the expanded entity can be calculated correctly. Previously, in absence of these keys the code was resulting in a NPE while building the location of the entity. > OData throws unknown error if $select is applied to expanded entity > ------------------------------------------------------------------- > > Key: TEIID-4045 > URL: https://issues.jboss.org/browse/TEIID-4045 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > *Result:* OData Library: An exception without message text was thrown. > *Status code:* 500 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4018) Class loading issue using ProtoSchemaBuilder to register annotated pojo

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4018?page=com.atlassian.jira.plugin... ] Work on TEIID-4018 stopped by Van Halbert. ------------------------------------------ > Class loading issue using ProtoSchemaBuilder to register annotated pojo > ----------------------------------------------------------------------- > > Key: TEIID-4018 > URL: https://issues.jboss.org/browse/TEIID-4018 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.12.x > > > Logic was changed in the infinispan dsl translator to use the ProtoSchemaBuilder to register the protobuf annotated pojo so that the marshaller(s) and protobuf definition files are not needed. However, there's an infinispan class loading issue that requires the upgrading to the protostream-3.0.5 version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4002) Configuring of JDG DSL resource adapter still requires marshaller and protobuf when using annotations to define schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4002?page=com.atlassian.jira.plugin... ] Work on TEIID-4002 stopped by Van Halbert. ------------------------------------------ > Configuring of JDG DSL resource adapter still requires marshaller and protobuf when using annotations to define schema > ---------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4002 > URL: https://issues.jboss.org/browse/TEIID-4002 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > > To improve the usability of JDG as a materialized data source, the resource-adapter needs to be changed to not require the marshaller/protobuf file when the the pojo class has the defined annotations for specifying the schema. > Currently, the marshaller(s) and protobuf are required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4043) If some functionality is not supported then OData should return status code 501 instead of 500

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4043?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4043. --------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done Implemented $top, $skip and $count. The $count testcase is still wrong as pending OLINGO-912. It will work correctly once the next update with Olingo library. If query issued with $level or nested $expand the service will result in 501. > If some functionality is not supported then OData should return status code 501 instead of 500 > ---------------------------------------------------------------------------------------------- > > Key: TEIID-4043 > URL: https://issues.jboss.org/browse/TEIID-4043 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > *URLs:* > - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > None of these options is implemented, but OData service for every request returns status code 500. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4038) OData returns bad number of entities with $count and $expand

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4038?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4038. --------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done Labels: Alpha3 (was: ) > OData returns bad number of entities with $count and $expand > ------------------------------------------------------------ > > Key: TEIID-4038 > URL: https://issues.jboss.org/browse/TEIID-4038 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Expected count:* 4 > *Actual count:* 9 > Similar behavior with $filter - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > OData should return only count of Customer entities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4045) OData throws unknown error if $select is applied to expanded entity

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4045?page=com.atlassian.jira.plugin... ] Work on TEIID-4045 started by Ramesh Reddy. ------------------------------------------- > OData throws unknown error if $select is applied to expanded entity > ------------------------------------------------------------------- > > Key: TEIID-4045 > URL: https://issues.jboss.org/browse/TEIID-4045 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > *Result:* OData Library: An exception without message text was thrown. > *Status code:* 500 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4083) MongoDB: Can't connect to mongodb using username/password auth

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4083?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4083. ----------------------------------- Resolution: Rejected Resolving based upon the comments. > MongoDB: Can't connect to mongodb using username/password auth > -------------------------------------------------------------- > > Key: TEIID-4083 > URL: https://issues.jboss.org/browse/TEIID-4083 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.5 > Environment: MongoDB 3.x > DV 6.3 ER1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Fix For: 8.12.5 > > > I can't connect to MongoDB through mongodb translator. An authentication always fails. > Server exception: > {code} > 14:14:15,304 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker3_QueryProcessorQueue4) mongodb-ds: getConnection(null, null) [0/20] > 14:14:15,305 INFO [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue4) SELECT smalla.INTNUM AS c_0, smalla.BIGDECIMALVALUE AS c_1, smalla.BIGINTEGERVALUE AS c_2, smalla.BOOLEANVALUE AS c_3, smalla.BYTENUM AS c_4, smalla.CHARVALUE AS c_5, smalla.DATEVALUE AS c_6, smalla.DOUBLENUM AS c_7, smalla.FLOATNUM AS c_8, smalla.INTKEY AS c_9, smalla.LONGNUM AS c_10, smalla.OBJECTVALUE AS c_11, smalla.SHORTVALUE AS c_12, smalla.STRINGKEY AS c_13, smalla.STRINGNUM AS c_14, smalla.TIMESTAMPVALUE AS c_15, smalla.TIMEVALUE AS c_16 FROM smalla LIMIT 100 > 14:14:16,229 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue4) Connector worker process failed for atomic-request=ysa307n2BRiE.1.0.1: org.teiid.translator.TranslatorException: { "serverUsed" : "dvqe03.mw.lab.eng.bos.redhat.com:27017" , "ok" : 0.0 , "errmsg" : "auth failed" , "code" : 18} > at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:104) [translator-mongodb-8.12.5.redhat-2.jar:8.12.5.redhat-2] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:359) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45] > at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy125.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_45] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] > Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "dvqe03.mw.lab.eng.bos.redhat.com:27017" , "ok" : 0.0 , "errmsg" : "auth failed" , "code" : 18} > at com.mongodb.CommandResult.getException(CommandResult.java:76) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.CommandResult.throwOnError(CommandResult.java:140) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBPort$NativeAuthenticator.authenticate(DBPort.java:986) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBPort.authenticate(DBPort.java:432) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBPort.checkAuth(DBPort.java:443) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:289) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:269) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:84) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DB.command(DB.java:320) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DB.command(DB.java:299) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:99) [mongo-java-driver-2.13.1.jar:] > at com.mongodb.DBCollection.aggregate(DBCollection.java:1649) [mongo-java-driver-2.13.1.jar:] > at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:102) [translator-mongodb-8.12.5.redhat-2.jar:8.12.5.redhat-2] > ... 18 more > 14:14:16,238 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker2_QueryProcessorQueue5) mongodb-ds: returnConnection(12a738da, false) [1/20] > 14:14:16,240 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue5) TEIID30020 > {code} > MongoDB log: > {code} > 16.141-0400 I ACCESS [conn704] authenticate db: bqt { authenticate: 1, user: "dv", nonce: "xxx", key: "xxx" } > 2016-03-16T09:14:16.141-0400 I ACCESS [conn704] Failed to authenticate dv@bqt with mechanism MONGODB-CR: AuthenticationFailed: MONGODB-CR credentials missing in the user document > {code} > You can find resource-adapter config in the corresponding bugzilla. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016