[JBoss JIRA] (TEIID-4552) Missing support for connection to Facebook via OAuth 2
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4552?page=com.atlassian.jira.plugin... ]
Jan Stastny updated TEIID-4552:
-------------------------------
Component/s: Misc. Connectors
> Missing support for connection to Facebook via OAuth 2
> ------------------------------------------------------
>
> Key: TEIID-4552
> URL: https://issues.jboss.org/browse/TEIID-4552
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.12.5
> Reporter: Lucie Fabrikova
> Assignee: Kylin Soong
> Fix For: 9.2
>
> Attachments: facebook3-vdb.xml, query, server.log, standalone.xml, teiid-oauth-util.sh-output
>
>
> I would like to connect to facebook resource adapter and configure OAuth 2 security domain for it; I used teiid-oauth-util.sh to generate the security domain (see attachment). Facebook doesn't support refresh tokens and in the generated code is refresh token's value "null".
> If I try to execute VDB with source pointing to such resource adapter I get error:
> ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=Gapuea1/NRcn.6.3.0: org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException
>
> (see server.log, facebook-vdb.xml, standalone.xml)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4707) upgrade pre-intalled PrestoDB driver
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4707?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4707:
------------------------------------
Steven, yes, there is no components depend on driver, I have reviewed from code base side, and verifed via wildfly server with quick starts.
> upgrade pre-intalled PrestoDB driver
> ------------------------------------
>
> Key: TEIID-4707
> URL: https://issues.jboss.org/browse/TEIID-4707
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> Upstream code pre-installed presto-jdbc-0.89.jar as prestoDB driver, there are almost 80 later version after 0.89, we may need upgrade to a later version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4703) The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database.
by SHI HONG CHIN (JIRA)
[ https://issues.jboss.org/browse/TEIID-4703?page=com.atlassian.jira.plugin... ]
SHI HONG CHIN commented on TEIID-4703:
--------------------------------------
Well, after I apply the workaround, and the workaround succeed, the Teiid database has been in heavy use. I will need to find a chance when nobody use the database, then try to reproduce the error and get the logs.
As the logs may contain some confidential information, I need some time to change the confidential information to fake. Or, is there anyway I can send the logs and VDB to you privately?
(Restricted to jira-users group)
> The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4703
> URL: https://issues.jboss.org/browse/TEIID-4703
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.13.4
> Reporter: SHI HONG CHIN
> Assignee: Steven Hawkins
>
> Database: Oracle + Firebird + Microsoft SQL Server.
> Oracle limit the maximum number of values in "IN" clause to 1000.
> In teiid, I am using the built-in Oracle translator.
> When running some SQL queries, Oracle database reported an error "No more data to read from socket". I had set the log level of Teiid to "ALL". According to the WildFly log files, Teiid executed a query with more than 10000 values in the "IN" clause.
> I tried to copy the whole SQL from WildFly log file into Oracle SQL Developer and execute it, the same error occurred. Then, I tried to edit the query by delete many values from the "IN" clause and then run the query again, and the query success.
> For teiid, as a workaround, I overrided the oracle translator and set the property of "MaxInCriteriaSize" to 50. After that, all SQL queries run success without any issue.
> I suggest that, by default, the built-in Oracle translator limit the number of values in "IN" clause to maximum 1000 values, and this behavior can be changed through properties.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4706) PrestoDBMetadataProcessor load metadata failed due to Duplicate Table
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4706?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4706:
-------------------------------
Fix Version/s: 9.2
> PrestoDBMetadataProcessor load metadata failed due to Duplicate Table
> ---------------------------------------------------------------------
>
> Key: TEIID-4706
> URL: https://issues.jboss.org/browse/TEIID-4706
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.2
> Environment: Scenario one
> * Presto 0.163 with one mysql catalog added
> * Teiid 9.2.0.Beta2-SNAPSHOT in embedded mode
> Scenario two
> * Presto 0.162 with one mysql catalog added(QE test environment)
> * Teiid 9.2.0.Beta2-SNAPSHOT server
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
> Attachments: TEIID4682Presto.java, module.zip, teiid4682-server-vdb.xml, teiid4682-vdb.xml
>
>
> PrestoDBMetadataProcessor use 'SHOW CATALOGS', 'SHOW TABLES FROM ...' to load tables from presto, presto default has a system catalog, in my test I only add one mysql catalog
> {code}
> SQL: SHOW CATALOGS
> +---------+
> | Catalog |
> +---------+
> | mysql |
> | system |
> +---------+
> {code}
> Note that both mysql and system has schema: *information_schema*:
> {code}
> SQL: SHOW SCHEMAS FROM mysql
> +--------------------+
> | Schema |
> +--------------------+
> | information_schema |
> | teiid |
> +--------------------+
> SQL: SHOW SCHEMAS FROM system
> +--------------------+
> | Schema |
> +--------------------+
> | information_schema |
> | jdbc |
> | metadata |
> | runtime |
> +--------------------+
> {code}
> Schema in different catalog contain the same tables
> {code}
> SQL: SHOW TABLES FROM mysql.information_schema
> +-------------------------+
> | Table |
> +-------------------------+
> | __internal_partitions__ |
> | columns |
> | schemata |
> | tables |
> | views |
> +-------------------------+
> SQL: SHOW TABLES FROM system.information_schema
> +-------------------------+
> | Table |
> +-------------------------+
> | __internal_partitions__ |
> | columns |
> | schemata |
> | tables |
> | views |
> +-------------------------+
> {code}
> Due the table name in both system.information_schema and mysql.information_schema has same table name, the *TEIID60013 Duplicate Table* through
> {code}
> Exception in thread "main" org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table __internal_partitions__
> at org.teiid.metadata.Schema.addTable(Schema.java:49)
> at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:231)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368)
> at org.teiid.translator.prestodb.PrestoDBMetadataProcessor.addTable(PrestoDBMetadataProcessor.java:147)
> at org.teiid.translator.prestodb.PrestoDBMetadataProcessor.getConnectorMetadata(PrestoDBMetadataProcessor.java:74)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:816)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:210)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:766)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:707)
> at org.teiid.test.teiid4699.TEIID4682Presto.main(TEIID4682Presto.java:41)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4706) PrestoDBMetadataProcessor load metadata failed due to Duplicate Table
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4706?page=com.atlassian.jira.plugin... ]
Kylin Soong resolved TEIID-4706.
--------------------------------
Resolution: Done
Add a notes in document(https://github.com/teiid/teiid-documents/pull/93) to resolve this issue.
> PrestoDBMetadataProcessor load metadata failed due to Duplicate Table
> ---------------------------------------------------------------------
>
> Key: TEIID-4706
> URL: https://issues.jboss.org/browse/TEIID-4706
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.2
> Environment: Scenario one
> * Presto 0.163 with one mysql catalog added
> * Teiid 9.2.0.Beta2-SNAPSHOT in embedded mode
> Scenario two
> * Presto 0.162 with one mysql catalog added(QE test environment)
> * Teiid 9.2.0.Beta2-SNAPSHOT server
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Attachments: TEIID4682Presto.java, module.zip, teiid4682-server-vdb.xml, teiid4682-vdb.xml
>
>
> PrestoDBMetadataProcessor use 'SHOW CATALOGS', 'SHOW TABLES FROM ...' to load tables from presto, presto default has a system catalog, in my test I only add one mysql catalog
> {code}
> SQL: SHOW CATALOGS
> +---------+
> | Catalog |
> +---------+
> | mysql |
> | system |
> +---------+
> {code}
> Note that both mysql and system has schema: *information_schema*:
> {code}
> SQL: SHOW SCHEMAS FROM mysql
> +--------------------+
> | Schema |
> +--------------------+
> | information_schema |
> | teiid |
> +--------------------+
> SQL: SHOW SCHEMAS FROM system
> +--------------------+
> | Schema |
> +--------------------+
> | information_schema |
> | jdbc |
> | metadata |
> | runtime |
> +--------------------+
> {code}
> Schema in different catalog contain the same tables
> {code}
> SQL: SHOW TABLES FROM mysql.information_schema
> +-------------------------+
> | Table |
> +-------------------------+
> | __internal_partitions__ |
> | columns |
> | schemata |
> | tables |
> | views |
> +-------------------------+
> SQL: SHOW TABLES FROM system.information_schema
> +-------------------------+
> | Table |
> +-------------------------+
> | __internal_partitions__ |
> | columns |
> | schemata |
> | tables |
> | views |
> +-------------------------+
> {code}
> Due the table name in both system.information_schema and mysql.information_schema has same table name, the *TEIID60013 Duplicate Table* through
> {code}
> Exception in thread "main" org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table __internal_partitions__
> at org.teiid.metadata.Schema.addTable(Schema.java:49)
> at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:231)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368)
> at org.teiid.translator.prestodb.PrestoDBMetadataProcessor.addTable(PrestoDBMetadataProcessor.java:147)
> at org.teiid.translator.prestodb.PrestoDBMetadataProcessor.getConnectorMetadata(PrestoDBMetadataProcessor.java:74)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:816)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:210)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:766)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:707)
> at org.teiid.test.teiid4699.TEIID4682Presto.main(TEIID4682Presto.java:41)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4715) Google translator allows to be inserted larger value than defined for teiid datatype
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created TEIID-4715:
--------------------------------------
Summary: Google translator allows to be inserted larger value than defined for teiid datatype
Key: TEIID-4715
URL: https://issues.jboss.org/browse/TEIID-4715
Project: Teiid
Issue Type: Bug
Affects Versions: 9.2
Reporter: Lucie Fabrikova
Assignee: Steven Hawkins
It is possible to insert larger value than defined by the teiid datatype, see query:
INSERT INTO SmallA (IntKey, BigIntegerValue) VALUES (100, 1234567890123456789012345)
But if I try to select the value, null is returned for BigIntegerValue:
SELECT IntKey, BigIntegerValue FROM SmallA WHERE IntKey=100
(VDB is same as in TEIID-4714)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4714) Google translator allows to be inserted duplicate key
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created TEIID-4714:
--------------------------------------
Summary: Google translator allows to be inserted duplicate key
Key: TEIID-4714
URL: https://issues.jboss.org/browse/TEIID-4714
Project: Teiid
Issue Type: Bug
Affects Versions: 9.2
Reporter: Lucie Fabrikova
Assignee: Steven Hawkins
Attachments: googlespreadsheetcrud-vdb.xml
It is possible to insert duplicate key, e.g. by running following query multiple times:
INSERT INTO SmallA (IntKey, StringKey) VALUES (1, '1')
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months