[JBoss JIRA] (TEIID-2914) Infinispan Connector didn't have the advanced searching option exposed
by Van Halbert (JIRA)
Van Halbert created TEIID-2914:
----------------------------------
Summary: Infinispan Connector didn't have the advanced searching option exposed
Key: TEIID-2914
URL: https://issues.jboss.org/browse/TEIID-2914
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.7, 8.7.1
Reporter: Van Halbert
Assignee: Van Halbert
The advanced searching option (i.e, lucene searching) that is defined in the .rar was not being picked up in the connector.
Also, it was incorrectly defined on the translator, because the translator cannot override how the cache is configured.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (TEIID-2915) Support consuming REST based service that is secured by Kerberos
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2915:
-----------------------------------
Summary: Support consuming REST based service that is secured by Kerberos
Key: TEIID-2915
URL: https://issues.jboss.org/browse/TEIID-2915
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.7.1
Add SSO based support for consuming the REST based services that are secured by Kerberos.
In order to support Kerberos at data source level, the engine needs to support Credential Delegation, then it can be used with CXF as shown in
http://cxf.apache.org/docs/jaxrs-kerberos.html#JAXRSKerberos-CredentialDe...
The SPENGO module needs to check getCredDelegState() flag on the GSS Context, and should provide a way to return the GSSCredential object then Teiid needs to propagate this as session payload and use it in the web-service connector as the delegate to target consumer service.
As of JBoss EAP 6.1.Alpha, I do not see the delegation in the SPENGO module, so support needs to be available in SPENGO module. Needs to investigate which version of SPENGO module supports this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
Grant-all is still useful. What I was referring to was how you could associate a security-domain to the vdb. Prior to TEIID-2863 you had to associate a security domain that was in the list on the transport. After that change you should be able to use any.
> Enable/disable transport per model/view/virtual procedure
> ---------------------------------------------------------
>
> Key: TEIID-2761
> URL: https://issues.jboss.org/browse/TEIID-2761
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.5
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
> One may want to have access to virtual procedures only by Odata for example.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (TEIID-2913) Enhance Logging Quickstart
by Van Halbert (JIRA)
Van Halbert created TEIID-2913:
----------------------------------
Summary: Enhance Logging Quickstart
Key: TEIID-2913
URL: https://issues.jboss.org/browse/TEIID-2913
Project: Teiid
Issue Type: Enhancement
Components: Quick Starts
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Van Halbert
Add the following enhancements to the logging quick start:
- add example for audit logging to a database (use h2)
- add dynamic VDB's to expose the audit and command logging schemas
- add a preconfigured dashboard to present the audit and command logs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (TEIID-2910) HIVE: method not found exception
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2910?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2910.
---------------------------------
Labels: CR2 Teiid (was: Teiid)
Resolution: Done
Fixed regression to use "createMetadataProcessor" to use correct metadata processor.
> HIVE: method not found exception
> ---------------------------------
>
> Key: TEIID-2910
> URL: https://issues.jboss.org/browse/TEIID-2910
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 8.7
> Environment: HIVE 0.11 driver with Teiid 8.7 CR1
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: Teiid, CR2
>
> I just upgraded from Teiid 8.7 BETA1 to Teiid 8.7 BETA1. And I got the following exception when trying to connect to HIVE1/ HIVE2 with HIVE 0.11 driver.
> Caused by: java.sql.SQLException: Method not supported
> at org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData.getIdentifierQuoteString(HiveDatabaseMetaData.java:391)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:105)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:309)
> And it used to work with Teiid 8.7 BETA1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (TEIID-2912) Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2912?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2912:
-------------------------------------
Those look like MS Access SYSTEM tables, may be you can use "excludeTables" or "tableNamePattern" to only import certain tables as a work-around.
> Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
> --------------------------------------------------------------
>
> Key: TEIID-2912
> URL: https://issues.jboss.org/browse/TEIID-2912
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, ODBC
> Affects Versions: 8.4
> Reporter: Filip Nguyen
> Priority: Blocker
> Attachments: server-importKeysFalse.log, server.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="testVDB" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <model name="testAccessModel" type="PHYSICAL" visible="true">
> <source name="testAccessModel" translator-name="jdbc-simple" connection-jndi-name="java:/AccessDS" />
> </model>
> </vdb>
> {code}
> Log exceprt (full log attached):
> {noformat}
> ory] (teiid-async-threads - 4) Driver loaded and instance created:sun.jdbc.odbc.JdbcOdbcDriver@49dd4a28
> 08:32:23,935 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing tables
> 08:32:23,952 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing columns
> 08:32:23,985 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing primary keys
> 08:32:23,985 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 4) AccessDS: returnConnection(2677c1e5, false) [1/20]
> 08:32:23,985 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB testVDB.1 model "testAccessModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: [Microsoft][ODBC Driver Manager] Driver does not support this function
> {noformat}
> Driver (standalone.xml attached):
> {code:xml}
> <datasource jndi-name="java:/AccessDS" pool-name="AccessDS" enabled="true">
> <connection-url>jdbc:odbc:AccessDS</connection-url>
> <driver>odbc</driver>
> <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
> <pool>
> <prefill>false</prefill>
> <use-strict-min>false</use-strict-min>
> <flush-strategy>FailingConnectionOnly</flush-strategy>
> </pool>
> </datasource>
> ...
> <drivers>
> <driver name="odbc" module="sun.jdk">
> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
> </driver>
> </drivers>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (TEIID-2912) Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2912?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2912:
---------------------------------------
So there is also an issue with getcolumns. I would say that this should not be treated as a blocker as it may require a new translator and the jdbc odbc bridge is deprecated and has been removed from java 8
> Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
> --------------------------------------------------------------
>
> Key: TEIID-2912
> URL: https://issues.jboss.org/browse/TEIID-2912
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, ODBC
> Affects Versions: 8.4
> Reporter: Filip Nguyen
> Priority: Blocker
> Attachments: server-importKeysFalse.log, server.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="testVDB" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <model name="testAccessModel" type="PHYSICAL" visible="true">
> <source name="testAccessModel" translator-name="jdbc-simple" connection-jndi-name="java:/AccessDS" />
> </model>
> </vdb>
> {code}
> Log exceprt (full log attached):
> {noformat}
> ory] (teiid-async-threads - 4) Driver loaded and instance created:sun.jdbc.odbc.JdbcOdbcDriver@49dd4a28
> 08:32:23,935 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing tables
> 08:32:23,952 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing columns
> 08:32:23,985 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing primary keys
> 08:32:23,985 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 4) AccessDS: returnConnection(2677c1e5, false) [1/20]
> 08:32:23,985 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB testVDB.1 model "testAccessModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: [Microsoft][ODBC Driver Manager] Driver does not support this function
> {noformat}
> Driver (standalone.xml attached):
> {code:xml}
> <datasource jndi-name="java:/AccessDS" pool-name="AccessDS" enabled="true">
> <connection-url>jdbc:odbc:AccessDS</connection-url>
> <driver>odbc</driver>
> <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
> <pool>
> <prefill>false</prefill>
> <use-strict-min>false</use-strict-min>
> <flush-strategy>FailingConnectionOnly</flush-strategy>
> </pool>
> </datasource>
> ...
> <drivers>
> <driver name="odbc" module="sun.jdk">
> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
> </driver>
> </drivers>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months