[JBoss JIRA] (TEIID-2605) Optimization substitutes wrong column in where clause
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2605?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2605.
---------------------------------
> Optimization substitutes wrong column in where clause
> -----------------------------------------------------
>
> Key: TEIID-2605
> URL: https://issues.jboss.org/browse/TEIID-2605
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.1
> Environment: z/OS
> Reporter: Jeff Hayes
> Assignee: Steven Hawkins
> Attachments: query_plan.txt, views.xml
>
>
> Optimization results in a query with a different column in the WHERE clause producing an empty result set.
> Full query plan is attached but the beginning and ending queries are shown below. Note that the subject column of the IN clause is SCOPEID but optimization changes it to AUTHID for some reason.
> USER COMMAND:
> SELECT * FROM SECURITY.SCPXREF AS CHORUS_B WHERE (CHORUS_B.SYSID = 'DE29') AND ((CHORUS_B.SCOPEID IN (SELECT SN5.SCOPEID FROM SECURI
> TY.SCPNEXT AS SN5 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN4.SCOPEID FROM SECURITY.SCPNEXT AS SN4 WHERE (SYSID = 'DE29') AND
> (NEXTREC IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURI
> TY.SCPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))))))) OR (CHORUS_B.SCOPEID IN (SELECT SN4.SCOPEID FROM SECURIT
> Y.SCPNEXT AS SN4 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND
> (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURITY.SCPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))))) OR (CHORUS_B.SC
> OPEID IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURITY.S
> CPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))) OR (CHORUS_B.SCOPEID IN (SELECT SN2.SCOPEID FROM SECURITY.SCPNEX
> T AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))) OR (CHORUS_B.SCOPEID = 'CHRDEPT1'))
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(10) output=[x.sysid AS sysid, x.scopeid AS authid, x.authid AS scopeid, x.authtype AS authtype] SELECT g_0.SYSID, g_0.SCO
> PEID, g_0.AUTHID, g_0.AUTHTYPE FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPXREF AS g_0 WHERE (g_0.SYSID = 'DE29') AND ((g_0.AUTHID IN
> (SELECT g_1.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_1 WHERE (g_1.SYSID = 'DE29') AND (g_1.NEXTREC IN (SELECT g_2
> .SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_2 WHERE (g_2.SYSID = 'DE29') AND (g_2.NEXTREC IN (SELECT g_3.SCOPEID FR
> OM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_3 WHERE (g_3.SYSID = 'DE29') AND (g_3.NEXTREC IN (SELECT g_4.SCOPEID FROM SECURITY
> _CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_4 WHERE (g_4.SYSID = 'DE29') AND (g_4.NEXTREC = 'CHRDEPT1'))))))))) OR (g_0.AUTHID IN (SELECT
> g_5.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_5 WHERE (g_5.SYSID = 'DE29') AND (g_5.NEXTREC IN (SELECT g_6.SCOPEI
> D FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_6 WHERE (g_6.SYSID = 'DE29') AND (g_6.NEXTREC IN (SELECT g_7.SCOPEID FROM SECU
> RITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_7 WHERE (g_7.SYSID = 'DE29') AND (g_7.NEXTREC = 'CHRDEPT1'))))))) OR (g_0.AUTHID IN (SELE
> CT g_8.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_8 WHERE (g_8.SYSID = 'DE29') AND (g_8.NEXTREC IN (SELECT g_9.SCOP
> EID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_9 WHERE (g_9.SYSID = 'DE29') AND (g_9.NEXTREC = 'CHRDEPT1'))))) OR (g_0.AUTH
> ID IN (SELECT g_10.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_10 WHERE (g_10.SYSID = 'DE29') AND (g_10.NEXTREC = 'C
> HRDEPT1'))) OR (g_0.AUTHID = 'CHRDEPT1'))
> The view definitions are shown below:
> <view name="SCPNEXT">
> <columns>
> <column name="sysid" type="varchar"/>
> <column name="scopeid" type="varchar"/>
> <column name="nextrec" type="varchar"/>
> </columns>
> <definition>
> #if ($db.count("select count(*) from sys.tables where Name='config' and SchemaName = 'security_db'") > 0)
> #set ($count = 0)
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> #if ($db.count("select count(*) from sys.tables where SchemaName = 'SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}'") == 0)
> #set ($count = $count + 1)
> #end
> #end
> #if ($count == 0)
> SELECT t.sysid, t.scopeid, t.nextrec
> FROM (
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> SELECT n.sysid, n.scopeid, n.nextrec
> FROM SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}.SCPNEXT n
> #if( $velocityHasNext ) UNION #end
> #end
> ) AS t
> #end
> #end
> </definition>
> </view>
> <view name="SCPXREF">
> <columns>
> <column name="sysid" type="varchar"/>
> <column name="authid" type="varchar"/>
> <column name="scopeid" type="varchar"/>
> <column name="authtype" type="varchar"/>
> </columns>
> <definition>
> #if ($db.count("select count(*) from sys.tables where Name='config' and SchemaName = 'security_db'") > 0)
> #set ($count = 0)
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> #if ($db.count("select count(*) from sys.tables where SchemaName = 'SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}'") == 0)
> #set ($count = $count + 1)
> #end
> #end
> #if ($count == 0)
> SELECT sysid, scopeid, authid, authtype
> FROM (
> #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'"))
> SELECT x.sysid, x.scopeid, x.authid, x.authtype
> FROM SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}.SCPXREF x
> #if( $velocityHasNext ) UNION #end
> #end
> ) AS t
> #end
> #end
> </definition>
> </view>
> I guess the best way to test this is to define these views and run the input query with SHOWPLAN=DEBUG and see if the AUTHID substitution is occurring.
> Thanks!
--
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
1 month, 2 weeks
[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
11 years, 8 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
11 years, 8 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
11 years, 8 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
11 years, 8 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
11 years, 8 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
11 years, 8 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
11 years, 8 months