[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2875:
---------------------------------------
> TEIID31152 More the one constraint with the name my-model.my-schema.MY-FOREIGN_KEY_CONSTRAINT_NAME
I think that the check added for TEIID-2922 may be over zealous - or at least that the importer should auto-resolve name conflicts because I think this is the second time we've seen behavior like this where the same constraint, at least by name, is repeated in the metadata. Could you log an issue, possibly with DDL that highlights the situation?
> Taking into account that this VDB is going to be used mostly for reading (select querying), how do you think the performance of the VDB is affected by setting the above property?
Knowing the keys assists with planning especially if you have federated joins. If you are going mostly against a single source it's more of an issue of what metadata is reported to your consuming app by Teiid.
> Also, is there a way to exclude the individual constraints that are causing the error ?
Unfortunately no. There is a more specific importForeignKeys importer setting though that you could use.
> Metadata failed to load. No column found
> ----------------------------------------
>
> Key: TEIID-2875
> URL: https://issues.jboss.org/browse/TEIID-2875
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.6
> Environment: Windows server 2003, Windows 7.
> Reporter: SHI HONG CHIN
> Assignee: Steven Hawkins
> Attachments: JakkerData-vdb.xml
>
>
> Affected database: Oracle
> The following error displayed when Teiid loading a dynamic VDB:
> 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not.
> This bug does not exist in version 8.5.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIID-3317) MongoDB: group by doesn't work with MongoDB 2.6.3
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3317?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3317:
---------------------------------------
Thanks, now we'll be doubly covered.
> 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
[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found
by Camilo Ortiz (JIRA)
[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ]
Camilo Ortiz commented on TEIID-2875:
-------------------------------------
Steven, thanks again for your accurate help. Fortunately, following the schemaName.tableName syntax, I was able to exclude the tables that were generating that error using the importer.excludeTables property. However, it seems that this legacy Oracle DB has another problem when loading the tables, showing warning messages as the following:
TEIID31152 More the one constraint with the name my-model.my-schema.MY-FOREIGN_KEY_CONSTRAINT_NAME
I was able to solve this by setting
<property name="importer.importKeys" value="false"/>
Taking into account that this VDB is going to be used mostly for reading (select querying), how do you think the performance of the VDB is affected by setting the above property? Also, is there a way to exclude the individual constraints that are causing the error ?
Thank you.
> Metadata failed to load. No column found
> ----------------------------------------
>
> Key: TEIID-2875
> URL: https://issues.jboss.org/browse/TEIID-2875
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.6
> Environment: Windows server 2003, Windows 7.
> Reporter: SHI HONG CHIN
> Assignee: Steven Hawkins
> Attachments: JakkerData-vdb.xml
>
>
> Affected database: Oracle
> The following error displayed when Teiid loading a dynamic VDB:
> 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not.
> This bug does not exist in version 8.5.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIID-3317) MongoDB: group by doesn't work with MongoDB 2.6.3
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3317?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3317:
-------------------------------------
if it is duplicate the test should be already there https://source.jboss.org/browse/Teiid/connectors/translator-mongodb/src/t...
> 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
[JBoss JIRA] (TEIID-3317) MongoDB: group by doesn't work with MongoDB 2.6.3
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3317?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3317.
-----------------------------------
Resolution: Duplicate Issue
I can see that array index out of bounds was addressed. I'll add a specific unit test for the next method.
> 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
[JBoss JIRA] (TEIID-2384) Managing Spatial Data Types
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2384?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2384:
---------------------------------------
The change have been made to make the type non-comparable. Also the oracle, pg, and mysql translators have been updated to utilize the source srid.
> Managing Spatial Data Types
> ---------------------------
>
> Key: TEIID-2384
> URL: https://issues.jboss.org/browse/TEIID-2384
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: luca gioppo
> Assignee: Steven Hawkins
> Labels: spatial, types
> Fix For: 8.10
>
>
> It would be useful to be able to consume data from spatial database exposing the VDB as a spatial database to other application (imagine geoserver).
> TEIID could be strategic for merging georeferenced data and make it available to those systems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIID-3329) Rationalize older spatial support with the new
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3329:
-------------------------------------
Summary: Rationalize older spatial support with the new
Key: TEIID-3329
URL: https://issues.jboss.org/browse/TEIID-3329
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
MongoDB and Oracle had existing spatial support that should be updated to account for the new support if possible.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2875:
---------------------------------------
> but I obtain the same error.
The name that exclude tables is checking against is based upon the settings of the translator and the particulars of the db. By default the translator will use all source name parts - catalog and schema and no quoting - catalogName.schemaName.tableName. However Oracle does not report a catalog, so the name used for comparison would be just schemaName.tableName. So as long as the exclusion expression is written taken into account the name that's being compared, it should work.
> and run the query "select * from m1.t1, m2.t2 where m1.t1.field1=m2.t2.field2" , is this join done within Oracle DB's engine?
The engine will assume that models/schemas against the same translator/jndi source are effectively the same. You can double check the query plan to ensure that the pushdown happens as expected.
> Because, as far as I understand, the property importer.tableNamePattern only accepts a single table name.
It's a SQL like pattern. It can use the % and _ wildcards, but that can be limiting. excludeTables can also be written as a negation so that it includes only specific tables - https://docs.jboss.org/author/display/TEIID/JDBC+Translator
> Metadata failed to load. No column found
> ----------------------------------------
>
> Key: TEIID-2875
> URL: https://issues.jboss.org/browse/TEIID-2875
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.6
> Environment: Windows server 2003, Windows 7.
> Reporter: SHI HONG CHIN
> Assignee: Steven Hawkins
> Attachments: JakkerData-vdb.xml
>
>
> Affected database: Oracle
> The following error displayed when Teiid loading a dynamic VDB:
> 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not.
> This bug does not exist in version 8.5.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months