[
https://issues.jboss.org/browse/TEIID-2344?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2344.
-----------------------------------
Resolution: Done
Took the approach of adding new ExecutionFactory methods
isSourceRequiredForCapabilities
initCapabilities
If isSourceRequiredForCapabilities returns true (which will currently only the the case
for the specific JDBC translator subtypes that use the database version property), then
we'll attempt to pass a connection to the initCapabilities method.
If this fails, then we still allow planning to proceed and only fail if the final plan
form still accesses a source that was planned without capabilities. This prevents invalid
plans from ever being created, but is slightly different than the expectation of partial
results mode - so that may still need users to set a version manually.
Compatibility and configuration issues are in the release notes.
TEIID-2477 is required however as we're currently just setting the raw product
version, which needs better handling.
Determine database version automatically
----------------------------------------
Key: TEIID-2344
URL:
https://issues.jboss.org/browse/TEIID-2344
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4
It would be helpful if we could determine the database version automatically from the
database metadata rather than relying on the user setting. Of course if the property
setting is present we shouldn't override it.
--
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