[JBoss JIRA] (TEIID-4368) Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4368?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4368:
---------------------------------------
"SELECTOR a" is using a identifier as the selector. The parser expects a string: "SELECTOR 'a'"
> Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER
> -----------------------------------------------------------------
>
> Key: TEIID-4368
> URL: https://issues.jboss.org/browse/TEIID-4368
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: texttabvdb-vdb.xml
>
>
> Server fails to deploy dynamic vdb with models which contain following TextTable parameters: SELECTOR, ROW DELIMITER, HEADER.
> Part of server log:
> 10:24:02,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "texttabvdb-vdb.xml" (runtime-name: "texttabvdb-vdb.xml")
> 10:24:02,213 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model2" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,214 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model3" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,217 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB texttab.1 model "model2" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "COLUMNS col1 string [*]ROW[*] DELIMITER 'X'" at line 7, column 59.
> Was expecting: "escape" | "no" | "selector" | "skip" | "width" | "delimiter" | "quote" | "header" | "," | "(" ...
> 10:24:02,218 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB texttab.1 model "model3" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") COLUMNS a [*]HEADER[*] 'a' string" at line 7, column 52.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...
> 10:24:02,219 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model5" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,222 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 10:24 AM
> 10:24:02,298 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS015865: Replaced deployment "texttabvdb-vdb.xml" with deployment "texttabvdb-vdb.xml"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4271:
---------------------------------------
> taking them completely will be breaking change
Wouldn't you still have to use a property, such as "exclude-system-schema"?
> also why introduce multiple properties and provide targeted fix for salesforce
Yes, I'm suggesting that we do both if needed. However just excluding the system will suffice for now. For any significant volume of vdb/version, adding the same models as a config parameter is somewhat of a burden.
> Consume Teiid OData from Salesforce
> -----------------------------------
>
> Key: TEIID-4271
> URL: https://issues.jboss.org/browse/TEIID-4271
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Johnathon Lee
> Fix For: 8.12.x
>
>
> At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume.
> Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-4368) Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIID-4368?page=com.atlassian.jira.plugin... ]
Lucie Fabrikova commented on TEIID-4368:
----------------------------------------
I see, thanks for clarification... and what is wrong with the SELECTOR? Deploy gives this:
15:24:53,276 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31080 model5.v3 validation error: TEIID31100 Parsing error: Encountered "('a' SELECTOR [*]a[*] COLUMNS y" at line 1, column 40.
Was expecting: <STRINGVAL>
> Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER
> -----------------------------------------------------------------
>
> Key: TEIID-4368
> URL: https://issues.jboss.org/browse/TEIID-4368
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: texttabvdb-vdb.xml
>
>
> Server fails to deploy dynamic vdb with models which contain following TextTable parameters: SELECTOR, ROW DELIMITER, HEADER.
> Part of server log:
> 10:24:02,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "texttabvdb-vdb.xml" (runtime-name: "texttabvdb-vdb.xml")
> 10:24:02,213 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model2" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,214 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model3" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,217 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB texttab.1 model "model2" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "COLUMNS col1 string [*]ROW[*] DELIMITER 'X'" at line 7, column 59.
> Was expecting: "escape" | "no" | "selector" | "skip" | "width" | "delimiter" | "quote" | "header" | "," | "(" ...
> 10:24:02,218 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB texttab.1 model "model3" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") COLUMNS a [*]HEADER[*] 'a' string" at line 7, column 52.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...
> 10:24:02,219 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model5" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,222 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 10:24 AM
> 10:24:02,298 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS015865: Replaced deployment "texttabvdb-vdb.xml" with deployment "texttabvdb-vdb.xml"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4271:
-------------------------------------
I understand that system models are not needed, taking them completely will be breaking change, also why introduce multiple properties and provide targeted fix for salesforce. IMO, what I wrote is targeted general fix for these two scenarios. Only drawback is, this needs to be done for every VDB in question, but gives the most flexibility.
> Consume Teiid OData from Salesforce
> -----------------------------------
>
> Key: TEIID-4271
> URL: https://issues.jboss.org/browse/TEIID-4271
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Johnathon Lee
> Fix For: 8.12.x
>
>
> At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume.
> Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-3808) Informix translator - date/time/timestamp values are adjusted differently according to timezone
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3808?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3808:
------------------------------------------------
Debi Rieden <drieden(a)redhat.com> changed the Status of [bug 1362400|https://bugzilla.redhat.com/show_bug.cgi?id=1362400] from NEW to CLOSED
> Informix translator - date/time/timestamp values are adjusted differently according to timezone
> -----------------------------------------------------------------------------------------------
>
> Key: TEIID-3808
> URL: https://issues.jboss.org/browse/TEIID-3808
> Project: Teiid
> Issue Type: Quality Risk
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> The Informix translator adjusts only time value according to server's timezone. Timestamp values are adjusted only if 'DatabaseTimeZone' property is set. Date values are not adjusted at all.
> I am not sure what is Teiid's logic in this case. Is the difference between server's timezone and database's timezone taken into account? Or only the timezone of the database?
> -------------------
> Server's timezone - GMT+1
> DatabaseTimeZone property - not overridden
> Result:
> |time|date|timestamp|
> |01:00:00|2000-01-01|2000-01-01 00:00:00.0|
> Server's timezone - GMT+5
> DatabaseTimeZone property - not overridden
> Result:
> |time|date|timestamp|
> |05:00:00|2000-01-01|2000-01-01 00:00:00.0|
> Server's timezone - GMT+5
> DatabaseTimeZone property - GMT+1
> Result:
> |time|date|timestamp|
> |01:00:00|2000-01-01|2000-01-01 04:00:00.0|
> Server's timezone - GMT+5
> DatabaseTimeZone property - GMT-1
> Result (int this case
> |time|date|timestamp|
> |23:00:00|2000-01-01|2000-01-01 06:00:00.0|
> Informix:
> {code:sql}
> ...
> datevalue date,
> timevalue datetime hour to fraction(1),
> timestampvalue datetime year to fraction(1),
> ...
> {code}
> VDB - foreign table:
> {code:sql}
> ...
> DateValue date OPTIONS (NATIVE_TYPE 'date', NAMEINSOURCE 'datevalue'),
> TimeValue timestamp OPTIONS (NATIVE_TYPE 'datetime hour to fraction(1)', NAMEINSOURCE 'timevalue'),
> TimestampValue timestamp OPTIONS (NATIVE_TYPE 'datetime year to fraction(1)', NAMEINSOURCE 'timestampvalue'),
> ...
> {code}
> VDB - view:
> {code:sql}
> ...
> DateValue date,
> TimeValue time,
> TimestampValue timestamp,
> ...
> AS ... DateValue, convert(TimeValue, time), TimestampValue, ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-3808) Informix translator - date/time/timestamp values are adjusted differently according to timezone
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3808?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3808:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1362400, https://bugzilla.redhat.com/show_bug.cgi?id=1278724 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1278724)
> Informix translator - date/time/timestamp values are adjusted differently according to timezone
> -----------------------------------------------------------------------------------------------
>
> Key: TEIID-3808
> URL: https://issues.jboss.org/browse/TEIID-3808
> Project: Teiid
> Issue Type: Quality Risk
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> The Informix translator adjusts only time value according to server's timezone. Timestamp values are adjusted only if 'DatabaseTimeZone' property is set. Date values are not adjusted at all.
> I am not sure what is Teiid's logic in this case. Is the difference between server's timezone and database's timezone taken into account? Or only the timezone of the database?
> -------------------
> Server's timezone - GMT+1
> DatabaseTimeZone property - not overridden
> Result:
> |time|date|timestamp|
> |01:00:00|2000-01-01|2000-01-01 00:00:00.0|
> Server's timezone - GMT+5
> DatabaseTimeZone property - not overridden
> Result:
> |time|date|timestamp|
> |05:00:00|2000-01-01|2000-01-01 00:00:00.0|
> Server's timezone - GMT+5
> DatabaseTimeZone property - GMT+1
> Result:
> |time|date|timestamp|
> |01:00:00|2000-01-01|2000-01-01 04:00:00.0|
> Server's timezone - GMT+5
> DatabaseTimeZone property - GMT-1
> Result (int this case
> |time|date|timestamp|
> |23:00:00|2000-01-01|2000-01-01 06:00:00.0|
> Informix:
> {code:sql}
> ...
> datevalue date,
> timevalue datetime hour to fraction(1),
> timestampvalue datetime year to fraction(1),
> ...
> {code}
> VDB - foreign table:
> {code:sql}
> ...
> DateValue date OPTIONS (NATIVE_TYPE 'date', NAMEINSOURCE 'datevalue'),
> TimeValue timestamp OPTIONS (NATIVE_TYPE 'datetime hour to fraction(1)', NAMEINSOURCE 'timevalue'),
> TimestampValue timestamp OPTIONS (NATIVE_TYPE 'datetime year to fraction(1)', NAMEINSOURCE 'timestampvalue'),
> ...
> {code}
> VDB - view:
> {code:sql}
> ...
> DateValue date,
> TimeValue time,
> TimestampValue timestamp,
> ...
> AS ... DateValue, convert(TimeValue, time), TimestampValue, ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-3715) MongoDB metadata import fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3715?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3715:
------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1246153|https://bugzilla.redhat.com/show_bug.cgi?id=1246153] from ON_QA to VERIFIED
> MongoDB metadata import fails
> -----------------------------
>
> Key: TEIID-3715
> URL: https://issues.jboss.org/browse/TEIID-3715
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 8.12.5
>
>
> Deploying the following dynamic vdb fails when Teiid Connection importer is used:
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="mongo" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <property name="deployment-name" value="mongo-vdb.xml" />
> <model name="importVDBSrcModel">
> <source name="importVDBSrcModel" translator-name="mongodb" connection-jndi-name="java:/mongoDS" />
> </model>
> </vdb>
> {code}
> The resource adapter is defined as:
> {code}
> <resource-adapter id="mongoDS">
> <module slot="main" id="org.jboss.teiid.resource-adapter.mongodb"/>
> <transaction-support>NoTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.mongodb.MongoDBManagedConnectionFactory" jndi-name="java:/mongoDS" enabled="true" use-java-context="true" pool-name="mongoDS">
> <config-property name="Database">
> bqt
> </config-property>
> <config-property name="RemoteServerList">
> vmgdb01.mw.lab.eng.bos.redhat.com:27017
> </config-property>
> <config-property name="Username">
> dv
> </config-property>
> <config-property name="Password">
> dv
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> Server log:
> {code}
> 08:26:05,590 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:not authorized for query on bqt.system.users: com.mongodb.MongoException: not authorized for query on bqt.system.users
> at com.mongodb.MongoException.parse(MongoException.java:82)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:292)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:273)
> at com.mongodb.DBCursor._check(DBCursor.java:368)
> at com.mongodb.DBCursor._hasNext(DBCursor.java:459)
> at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:58)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:39)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-3589) MongoDB metadata import fails with NPE
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3589?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3589:
------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1246153|https://bugzilla.redhat.com/show_bug.cgi?id=1246153] from ON_QA to VERIFIED
> MongoDB metadata import fails with NPE
> --------------------------------------
>
> Key: TEIID-3589
> URL: https://issues.jboss.org/browse/TEIID-3589
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Labels: Beta1, ER5
> Fix For: 8.7.1.6_2, 8.12
>
>
> Deploying the following dynamic vdb fails with a NullPointerException when Teiid Connection importer is used:
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="mongo" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <property name="deployment-name" value="mongo-vdb.xml" />
> <model name="importVDBSrcModel">
> <source name="importVDBSrcModel" translator-name="mongodb" connection-jndi-name="java:/mongoDS" />
> </model>
> </vdb>
> {code}
> The resource adapter is defined as:
> {code}
> <resource-adapter id="mongoDS">
> <module slot="main" id="org.jboss.teiid.resource-adapter.mongodb"/>
> <transaction-support>NoTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.mongodb.MongoDBManagedConnectionFactory" jndi-name="java:/mongoDS" enabled="true" use-java-context="true" pool-name="mongoDS">
> <config-property name="Database">
> bqt
> </config-property>
> <config-property name="RemoteServerList">
> vmgdb01.mw.lab.eng.bos.redhat.com:27017
> </config-property>
> <config-property name="Username">
> dv
> </config-property>
> <config-property name="Password">
> dv
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> Server log:
> {code}
> 16:46:49,793 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mongo-vdb.xml" (runtime-name: "mongo-vdb.xml")
> 16:46:49,809 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-5) VDB mongo-vdb.xml has been parsed.
> 16:46:49,835 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mongo.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 7/23/15 4:46 PM
> 16:46:49,869 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015859: Deployed "mongo-vdb.xml" (runtime-name : "mongo-vdb.xml")
> 16:46:50,626 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addTable(MongoDBMetadataProcessor.java:92)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:57)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:38)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4218:
------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1246153|https://bugzilla.redhat.com/show_bug.cgi?id=1246153] from ON_QA to VERIFIED
> MongoDB metadata import fails when user has insufficient permissions
> --------------------------------------------------------------------
>
> Key: TEIID-4218
> URL: https://issues.jboss.org/browse/TEIID-4218
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> The vdb deployment now fails with the following errror:
> 14:26:08,810 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:not authorized for query on bqt.system.users: com.mongodb.MongoEx
> ception: not authorized for query on bqt.system.users
> at com.mongodb.MongoException.parse(MongoException.java:82)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:292)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:273)
> at com.mongodb.DBCursor._check(DBCursor.java:368)
> at com.mongodb.DBCursor._hasNext(DBCursor.java:459)
> at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:58)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:39)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> The user does not have access to the system tables, but there is no way to exclude those tables from the import (like with the JDBC importer).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months