[teiid-issues] [JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13374608#comment-13374608 ] 

Steven Hawkins commented on TEIID-4218:
---------------------------------------

Should the exception be caught in the loop?  Or does the whole iteration become invalid after the first exception?

> 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
>              Labels: Alpaha1
>             Fix For: 9.3
>
>
> 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
(v7.2.3#72005)