February 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3345) NPE while accessing VDB via OData access

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3345?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3345: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1194292 > NPE while accessing VDB via OData access > ---------------------------------------- > > Key: TEIID-3345 > URL: https://issues.jboss.org/browse/TEIID-3345 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If wrong odata URL is provided, an internal error is displayed: > URL: http://localhost:8080/odata/ > Exception: org.teiid.core.TeiidRuntimeException: TEIID16008 VDB name not defined on the URL. The url format is http://{host}:{port}/odata/{vdb-name}[.{vdb-version}]/... > org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:88) > org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:47) > .... > This behavior is quite expected. > URL: http://localhost:8080/odata > Exception: java.lang.NullPointerException > org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:80) > org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:47) > ... > I expect that teiid should return similar exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3345) NPE while accessing VDB via OData access

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3345: ----------------------------------- Summary: NPE while accessing VDB via OData access Key: TEIID-3345 URL: https://issues.jboss.org/browse/TEIID-3345 Project: Teiid Issue Type: Bug Reporter: Juraj Duráni Assignee: Steven Hawkins If wrong odata URL is provided, an internal error is displayed: URL: http://localhost:8080/odata/ Exception: org.teiid.core.TeiidRuntimeException: TEIID16008 VDB name not defined on the URL. The url format is http://{host}:{port}/odata/{vdb-name}[.{vdb-version}]/... org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:88) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:47) .... This behavior is quite expected. URL: http://localhost:8080/odata Exception: java.lang.NullPointerException org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:80) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:47) ... I expect that teiid should return similar exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3302) Implement ST_Transform

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3302?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3302: ----------------------------------- Proj4j uploaded to central. Hoping to get started on ST_transform over weekend. > Implement ST_Transform > ---------------------- > > Key: TEIID-3302 > URL: https://issues.jboss.org/browse/TEIID-3302 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Implement [ST_Transform|http://postgis.org/docs/ST_Transform.html] system function. This would be used to transform geometry between different coordinate systems. This needs SPATIAL_REF_SYS table and a supporting library. > There are a couple of options for implementing this: > * http://trac.osgeo.org/proj4j/ - Port of the C library used by PostGIS. Fewest dependencies and should keep us close to PostGIS in capabilities. There will be a little boilerplate to interface with JTS. > * http://docs.geotools.org/latest/userguide/library/referencing/index.html - GeoTools referencing module. I think we would need to develop a simple plugin to interface with our SPATIAL_REF_SYS table. GeoTools is active and has good docs, but brings in a lot of dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3317) MongoDB: group by doesn't work with MongoDB 2.6.3

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-3317?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-3317: ---------------------------------- Thanks. It works in Teiid 8.10 CR1 with MongoDB 2.6.6. Thanks for fixing this issue. > MongoDB: group by doesn't work with MongoDB 2.6.3 > -------------------------------------------------- > > Key: TEIID-3317 > URL: https://issues.jboss.org/browse/TEIID-3317 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.9.1 > Environment: Teiid 8.9.1 with MongoDB version: 2.6.3 using MongoDB Driver mongo-java-driver-2.12.3.jar > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Teiid > > Running group by sql through exception: > select "FirstName" > from "MongoDB_Array_263"."TeiidArray" > group by "FirstName" > order by "FirstName" > limit 1000 > Exception: > Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) > at java.util.ArrayList.get(ArrayList.java:382) > at org.teiid.translator.mongodb.MongoDBQueryExecution.next(MongoDBQueryExecution.java:132) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:386) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:204) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:209) > at $Proxy182.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) > 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:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3316) MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-3316?page=com.atlassian.jira.plugin... ] Ivan Chan updated TEIID-3316: ----------------------------- Summary: MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1 (was: MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB using Teiid 8.9.1) > MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1 > -------------------------------------------------------------------------------------------------- > > Key: TEIID-3316 > URL: https://issues.jboss.org/browse/TEIID-3316 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.9.1 > Environment: Teiid 8.9.1 with MongoDB shell version: 2.4.8 using MongoDB Driver mongo-java-driver-2.12.3.jar > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.10 > > > I am getting the following erroe when connecting to MongoDB using Teiid 8.9.1: > Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "donetsk:27017" , "ok" : 0.0 , "errmsg" : "unrecognized field \"cursor"} > at com.mongodb.CommandResult.getException(CommandResult.java:76) > at com.mongodb.CommandResult.throwOnError(CommandResult.java:131) > at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:100) > at com.mongodb.DBCollection.aggregate(DBCollection.java:1571) > at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:111) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3316) MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB using Teiid 8.9.1

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-3316?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-3316: ---------------------------------- I think the issue is Teiid with MongoDB version 2.4.8. It works with MongoDB version 2.6.6. Update: I have tried to do a simple test without nested/ array JSON document with Teiid 8.10 CR1 against MongoDB version 2.4.8. But it still doesn't work with different exception: Caused by: java.lang.NullPointerException at org.teiid.translator.mongodb.MongoDBQueryExecution.close(MongoDBQueryExecution.java:144) at org.teiid.translator.mongodb.MongoDBQueryExecution.cancel(MongoDBQueryExecution.java:150) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.cancel(ConnectorWorkItem.java:191) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:209) at $Proxy183.cancel(Unknown Source) at org.teiid.dqp.internal.process.DataTierTupleSource.fullyCloseSource(DataTierTupleSource.java:323) at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:378) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:154) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) JSON Data: { "_id": { "$oid" : "52d7945f4acacbbae9c86304" }, "id": "fDxEleBZwLDLmIQH", "store_sales": 7.44, "product_category": "Jams and Jellies", "product_department": "Baking Goods", "product_family": "Food", "product_subcategory": "Jam", "store_city": "Los Angeles", "store_cost": 2.976, "store_country": "USA", "store_state": "CA", "the_date": "09/09/2012 0:00 -07:00", "unit_sales": 4 } Schema: CREATE FOREIGN TABLE sales ( saleID integer PRIMARY KEY, product_category varchar(255), product_family varchar(255), store_city varchar(255)) OPTIONS(UPDATABLE 'TRUE'); SQL: select "store_city" from "MongoDB_26"."sales" limit 1000 However, everything works fine if I run against with MongoDB version 2.6.6 > MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB using Teiid 8.9.1 > -------------------------------------------------------------------------------------------- > > Key: TEIID-3316 > URL: https://issues.jboss.org/browse/TEIID-3316 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.9.1 > Environment: Teiid 8.9.1 with MongoDB shell version: 2.4.8 using MongoDB Driver mongo-java-driver-2.12.3.jar > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.10 > > > I am getting the following erroe when connecting to MongoDB using Teiid 8.9.1: > Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "donetsk:27017" , "ok" : 0.0 , "errmsg" : "unrecognized field \"cursor"} > at com.mongodb.CommandResult.getException(CommandResult.java:76) > at com.mongodb.CommandResult.throwOnError(CommandResult.java:131) > at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:100) > at com.mongodb.DBCollection.aggregate(DBCollection.java:1571) > at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:111) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3325) Subquery hints in row based conditions not honored

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3325?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3325. ----------------------------------- Resolution: Done Added dependent join logic into the semi join planning. We need to eventually allow for uncorrelated subquery inline expansion rather than being processed as a dependent join - however more than likely that would still go through the dependent criteria processor logic to handle large numbers of values (which would only work for semi and not anti-semi scenarios) > Subquery hints in row based conditions not honored > -------------------------------------------------- > > Key: TEIID-3325 > URL: https://issues.jboss.org/browse/TEIID-3325 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Some of the subquery hints, such as DJ take affect during rewrite - which happens before security planning. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3295) Change subqueryUnnestDefault to true

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3295?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-3295: ----------------------------------- Reopening since there was an issue found with detecting when to apply distinct to the subquery and we can now apply dependent joins later in planning via TEIID-3325 > Change subqueryUnnestDefault to true > ------------------------------------ > > Key: TEIID-3295 > URL: https://issues.jboss.org/browse/TEIID-3295 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.10 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Since TEIID-2149 the scope of the property has been limited in scope and should be flipped to true to allow for more efficient planning. In the worst case users can use the NO_UNNEST hint to prevent the optimization. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3295) Change subqueryUnnestDefault to true

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3295?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3295: ---------------------------------- Fix Version/s: 8.11 (was: 8.10) > Change subqueryUnnestDefault to true > ------------------------------------ > > Key: TEIID-3295 > URL: https://issues.jboss.org/browse/TEIID-3295 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.10 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Since TEIID-2149 the scope of the property has been limited in scope and should be flipped to true to allow for more efficient planning. In the worst case users can use the NO_UNNEST hint to prevent the optimization. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3344) Querying server-generated REST WAR fails with NPE when parameter is of type string

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3344?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3344. --------------------------------- Labels: CR2 (was: ) Fix Version/s: 8.10 Resolution: Done Fixed the NPE > Querying server-generated REST WAR fails with NPE when parameter is of type string > ---------------------------------------------------------------------------------- > > Key: TEIID-3344 > URL: https://issues.jboss.org/browse/TEIID-3344 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.10 > > Attachments: stacktrace, virtualrest-vdb.xml > > > When the attached dynamic VDB is deployed, querying http://localhost:8080/sample_1/view/proc1/1 causes a NullPointerException (stacktrace from log attached). > Querying the other procedures in the VDB (proc2 - proc4, which are identical except for the type of the parameter) works as expected. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2015