[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
4:58 a.m.
[
https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2786:
----------------------------------
Attachment: mode.patch
Here's a minimal patch pulling out TEIID-2785. We don't want too much of the
internals of this class exposed as each extension point becomes something that we have to
support for quite a while.
Some of the property defaults, such as useFullSchemaName, should not be changed as they
are for the metadata presentation and do not affect how the metadata is fetched.
What is the rationale of overriding the table types? Typically specifying no table types
(null) would mean getting all, rather than just VIEW. Specifying empty seems like it
should return nothing.
Generally catching a sql feature not supported exception doesn't really work as you
don't know what the calling sequence was that triggered the exception - you may be
getting an invalid metadata subset.
Also ideally correcting the widenUnsignedTypes setter would be done in a separate issue so
that it could be pulled back more easily as an individual change.
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: Van Halbert
Fix For: 8.7
Attachments: mode.patch
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
4001
days inactive
4001
days old
0 comments
1 participants
participants (1)
-
Steven Hawkins (JIRA)