[JBoss JIRA] (TEIID-4800) Permissions should also specify object type
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4800:
-------------------------------------
Summary: Permissions should also specify object type
Key: TEIID-4800
URL: https://issues.jboss.org/browse/TEIID-4800
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.3
Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names.
Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-1684) Add a native type for InetAddresses
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1684?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-1684:
-------------------------------------
Fix Version/s: Open To Community
Assignee: (was: Steven Hawkins)
With TEIID-3624 we are now close to supporting extensible runtime types which would be preferable path toward adding a new type class.
> Add a native type for InetAddresses
> ------------------------------------
>
> Key: TEIID-1684
> URL: https://issues.jboss.org/browse/TEIID-1684
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Caleb Corliss
> Priority: Minor
> Fix For: Open To Community
>
>
> Currently, we are unable to work directly with INET columns (Oracle or PostgreSQL.) It would be nice if there was a native type that could map INET columns to java.net.Inet4Address and java.netInet6Address objects at some time in the near future.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4467) Google translator throws exception invalid_query for GROUP BY
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4467?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4467:
----------------------------------
Fix Version/s: 9.3.1
(was: 9.3)
Priority: Minor (was: Major)
> Google translator throws exception invalid_query for GROUP BY
> --------------------------------------------------------------
>
> Key: TEIID-4467
> URL: https://issues.jboss.org/browse/TEIID-4467
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Lucie Fabrikova
> Priority: Minor
> Fix For: 9.3.1
>
> Attachments: googlespreadsheet-vdb.xml, server.log
>
>
> Google translator produces following exception for a query: "SELECT IntKey FROM bqt1.SmallA GROUP BY IntKey":
> 16:27:26,955 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue14) TEIID30019 Unexpected exception for request vn+N1XY8Atf5.6: org.teiid.resource.adapter.google.common.SpreadsheetOperationException: [invalid_query]
> at org.teiid.resource.adapter.google.dataprotocol.GoogleDataProtocolAPI$DataProtocolQueryStrategy.executeAndParse(GoogleDataProtocolAPI.java:196)
> ...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4218:
---------------------------------------
Sorry, yes I missed the outer loop.
> 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)
9 years
[JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4218:
-------------------------------------
The iteration is on the retrieving the documents from the source for a given collection, so top level one should be good. This way, I can only omit the offending collection and continue with rest.
> 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)
9 years
[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3836.
-----------------------------------
Fix Version/s: (was: 9.3)
Resolution: Out of Date
Marking as out of date.
> Create a quick start to demonstrate OData
> -----------------------------------------
>
> Key: TEIID-3836
> URL: https://issues.jboss.org/browse/TEIID-3836
> Project: Teiid
> Issue Type: Task
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Van Halbert
>
> Add a quick start to demonstrate OData api may helpful for users.
> After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error:
> {code}
> TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin... ]
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)
9 years
[JBoss JIRA] (TEIID-4799) Accessing a JDBC source via ODATA creates stack trace in log
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4799?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4799:
---------------------------------------
I can't reproduce this in 8.12 nor master just based upon this description. Can the vdb be provided?
> Accessing a JDBC source via ODATA creates stack trace in log
> -------------------------------------------------------------
>
> Key: TEIID-4799
> URL: https://issues.jboss.org/browse/TEIID-4799
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: stacktrace.txt
>
>
> When doing a get to a odata endpoint that will use a jdbc connection in data virtualization, there will be a transaction related stacktrace in the logs. This does not seem to create a problem but is confusing.
> Version-Release number of selected component (if applicable):
> 8.12.x
> How reproducible:
> Steps to Reproduce:
> 1. Add a JDBC datasource model in the Teiid Design Perspective
> 2. Add a Teiid Metadata view model using the JDBC source model
> 3. Deploy the view model in a VDB
> 4. Access the view model via an odata call
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years