[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2786:
---------------------------------------
> But I'm not sure this is ModeShape issue, cause the dataType of the column is int.
It's fine to change those calls to getInt, but in general you would expect JDBC implementations to support getShort - at the very least as a wrapper/cast to getInt
> 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
>
>
> 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
10 years, 11 months
[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2786:
------------------------------------
Here are some initial observations that may require more work on the Modeshape side:
- we know ModeShape doesn't support certain methods (i.e., getTypeInfo(..), getIndexes) which some are going to be done in the future
- in the ModeShape metadata, an UNDEFINED type is being created and causing an issue. The value of the type is java.lang.Integer, but the jcr PropertyType's dosn't have an Integer. And because its UNDEFINED, when DatabaseMetaData.getColumns(..) is called, an error occurs in addColumns(…) method, row: int type = columns.getInt(5);
- In the same addColumns(..) method, row: column.setNullType(NullType.values()[columns.getShort(11)]);
fails because getShort(..) isn't implemented. But I'm not sure this is ModeShape issue, cause the dataType of the column is int.
After making some adjustments, more UNDEFINED types were seen. So a lot more has to be done here, but no time at the moment. I'll return to this at a later date.
> 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
>
>
> 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
10 years, 11 months
[JBoss JIRA] (TEIID-2780) Provide Translator for Apache SOLR
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2780?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2780:
-------------------------------------
Original contribution is from Mike Walker and Jason Marly from EDS/MetaMatrix.
Added translator, and JCA resource adapter for Apache SOLR.
1) Resource Adapter provides the connection to the SOLR, even though it uses http transport this does not use WS JCA adapter as SOLRJ client libraries available with SOLR project has used apache HTTP Client do the task
2) Translator is capable of select, insert, update and delete
3) Translator can also provide metadata, note that any given core will have single table
4) Translator provides equality, IN, LIKE based searches
5) Suports ORDER BY, ROW LIMIT
6) Multi-valued fields are resported as Array types in Teiid
Will resolve the issue once the documentation is added.
> Provide Translator for Apache SOLR
> ----------------------------------
>
> Key: TEIID-2780
> URL: https://issues.jboss.org/browse/TEIID-2780
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.7
>
>
> Create a translator for querying Apache SOLR
> http://lucene.apache.org/solr/
--
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, 11 months
[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2795:
----------------------------------
Attachment: TEIID-2795.patch
Here's a back port of the relevant changes from 8.4. It may also make some sense (perhaps a config option) to have the request that initiates the refresh perform a blocking refresh even in the ttl case.
> TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2795
> URL: https://issues.jboss.org/browse/TEIID-2795
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.8
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Attachments: TEIID-2795.patch
>
>
> using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load.
> Sequence of events
> 1) Execute the query to initiate the internal MV load
> 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache
> 3) Wait for 5 minutes for TTL to expire
> 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ...
> [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat...
--
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, 11 months
[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2795:
----------------------------------
Assignee: Johnathon Lee (was: Steven Hawkins)
> TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2795
> URL: https://issues.jboss.org/browse/TEIID-2795
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.8
> Reporter: Debbie Steigner
> Assignee: Johnathon Lee
> Attachments: TEIID-2795.patch
>
>
> using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load.
> Sequence of events
> 1) Execute the query to initiate the internal MV load
> 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache
> 3) Wait for 5 minutes for TTL to expire
> 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ...
> [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat...
--
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, 11 months
[JBoss JIRA] (TEIID-2795) TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-2795?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-2795:
----------------------------------------
Yes.
--
Debbie Steigner (dsteigne(a)redhat.com)
Red Hat Global Support Services
Principal Technical Support Engineer
> TTL Snapshot Refresh doesn't fully reload Internal MV if the user query contains LIMIT
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2795
> URL: https://issues.jboss.org/browse/TEIID-2795
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.8
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> using the cache hint to automatically trigger a full snapshot refresh after a specified time to live (TTL)[1]. The TTL works but if the user query that is run contains a LIMIT clause the refresh load uses the LIMIT and doesn't completely load the internal MV and fails load.
> Sequence of events
> 1) Execute the query to initiate the internal MV load
> 2) After caching, issue the same query but with limit of 10,000 to test it is hitting the cache
> 3) Wait for 5 minutes for TTL to expire
> 4) Re-issue the same query with limit of 10,000 and i can see the state change to reloading but once the query has finished fetching 10,000 from data source it terminates and the MV state changed to failed_load. I would have expected the MV to continue to load to rehydrate the cache and the query should be fetching the data from the stale cache. But this is not the case ...
> [1]https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Dat...
--
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, 11 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:
---------------------------------------
> Do the clients have to specify which security domain they have to use or is this implied by the server configuration?
The clients don't have to know anything specific. The security domains can be specific to the transport in the server configuration.
> 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
>
> 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, 11 months
[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Patrick Deenen (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Patrick Deenen commented on TEIID-2761:
---------------------------------------
What I think is still inconvenient about this, that multiple security domains have to be defined.
Do the clients have to specify which security domain they have to use or is this implied by the server configuration?
> 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
>
> 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, 11 months