[JBoss JIRA] (TEIID-2849) MongoDB: Provide basic metadata support
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2849?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2849.
---------------------------------
Resolution: Done
Minimal metadata support has been added. May not work complex documents, but this will provide a starting point for the user to further enhance.
> MongoDB: Provide basic metadata support
> ---------------------------------------
>
> Key: TEIID-2849
> URL: https://issues.jboss.org/browse/TEIID-2849
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: mongodb
> Fix For: 8.7
>
>
> Currently there is no native metadata import support in the MongoDB translator. It was avoided int he first run because there is no good way to interpret the complex document records. This position has not changed, but this enhancement request is to see if it can capture simple documents or top level documents as a starting point to capture and then to improve upon manually using tooling.
--
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, 7 months
[JBoss JIRA] (TEIID-2911) Applications that expose RESTEasy XML endpoints
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2911?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2911:
---------------------------------------
In looking at this a bit more, I believe the entity expansion is taking place in the odata4j layer - not RESTEasy. As you dig through the parser is created with XMLInputFactory.newInstance(), which I believe we would need to get javax.xml.stream.isSupportingExternalEntities=false passed to. The default is unspecified so I'm not sure if woodstox supports that by default or if there is a system wide way to disable. I believe the same would hold true for Teiid's own usage of XMLInputFactory.newInstance - it may be allowing SQL/XML to resolve external entities as well.
> Applications that expose RESTEasy XML endpoints
> -----------------------------------------------
>
> Key: TEIID-2911
> URL: https://issues.jboss.org/browse/TEIID-2911
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.4.1, 8.7, 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
>
> if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy:
> <context-param>
> <param-name>resteasy.document.expand.entity.references</param-name>
> <param-value>false</param-value>
> </context-param>
> Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element.
--
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, 7 months
[JBoss JIRA] (TEIID-2910) HIVE: method not found exception
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2910?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2910:
---------------------------------------
Probably 4/7. We need to see if there are any other immediate issues before cutting another CR.
> 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: Steven Hawkins
> Labels: Teiid
>
> 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, 7 months
[JBoss JIRA] (TEIID-2910) HIVE: method not found exception
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2910?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-2910:
----------------------------------
Thanks for looking into this issue. When do you guys plan to release CR2?
> 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: Steven Hawkins
> Labels: Teiid
>
> 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, 7 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:
-------------------------------------
in the model fragment
{code}
<property name="importer.importKeys" value="false"/>
{code}
> 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.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {noformat}
> <?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>
> {noformat}
> 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):
> {noformat}
> <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>
> {noformat}
--
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, 7 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:
---------------------------------------
Looks like import keys may need to be disabled. You should try the import with as few options enabled as possible.
> 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.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {noformat}
> <?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>
> {noformat}
> 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):
> {noformat}
> <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>
> {noformat}
--
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, 7 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:
-------------------------------------
Filip - Do you see metadata if you use jdbc-odbc bridge , but access it using SquirreL?
> 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.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {noformat}
> <?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>
> {noformat}
> 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):
> {noformat}
> <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>
> {noformat}
--
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, 7 months
[JBoss JIRA] (TEIID-2912) Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-2912?page=com.atlassian.jira.plugin... ]
Filip Nguyen updated TEIID-2912:
--------------------------------
Component/s: JDBC Connector
ODBC
> 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.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {noformat}
> <?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>
> {noformat}
> 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):
> {noformat}
> <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>
> {noformat}
--
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, 7 months