[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
11:35 a.m.
[
https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-2786:
------------------------------------
Ok, after changing the translator override to a model property, the VDB was now able to
become active. However, it disabled access to the datasource:
11:31:06,146 WARN [org.teiid.PROCESSOR] (New I/O worker #2) TEIID40011 Processing
exception 'TEIID31099 VDB Portfolio.1[ModeShape{ms-connector=ms-connector, modeshape,
java:/datasources/ModeShapeDSx}] is not active. Resubmit your query after loading has
completed or after the errors have been corrected.' for session h5xROU4+bDdh.
Exception type org.teiid.core.TeiidProcessingException thrown from
org.teiid.dqp.internal.process.DQPCore.checkActive(DQPCore.java:832). Enable more detailed
logging to see the entire stacktrace.
When connecting to VDB using Squirrel, no metadata for the data source is exposed. It
appears, if the typeInfo is not obtained, no table info is available either.
ModeShape ExecutionFactory.getMetadata fails with
java.sql.SQLFeatureNotSupportedException
------------------------------------------------------------------------------------------
Key: TEIID-2786
URL: https://issues.jboss.org/browse/TEIID-2786
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 7.7
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 8.7
When trying to use the Teiid Designer feature of importing using a Teiid Connection fails
when the connection is to ModeShape. The following exception:
08:33:44,914 ERROR [stderr] (teiid-async-threads - 2)
java.sql.SQLFeatureNotSupportedException
08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at
org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656)
08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107)
08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559:
Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280)
08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62)
08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.jboss.VDBService$6.run(VDBService.java:397)
08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at
org.teiid.jboss.VDBService$7.run(VDBService.java:444)
08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at
org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as
the remote JDBC version has been the one used when using the Modeshape eclipse plugin for
importing the metadata.
--
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
4026
days inactive
4026
days old
0 comments
1 participants
participants (1)
-
Van Halbert (JIRA)