[
https://issues.jboss.org/browse/TEIID-3955?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3955:
---------------------------------------
Note that by logging something as a WARNING doesn't mean that it's not a problem,
it just means that the system will continue to operate as normal and that it is an
expected failure condition. Just like when someone issues a failing SQL query.
At most you would want to offer an option to ignore errors - but the logic would need
tweaking as to how to recover (removing invalid tables, etc.)
When the JDBC MetadataProcessor is reverse engineering, don't
fail the VDB when there are warning on the metadata load
----------------------------------------------------------------------------------------------------------------------
Key: TEIID-3955
URL:
https://issues.jboss.org/browse/TEIID-3955
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
When the JDBC metadata processor is reverse engineering the metadata and there are
WARNINGS that it could not create the metadata for parts (not all) of the tables, then
allow the VDB to be active, instead of failing it and making it inactive. Let the
developer decide if what was not loaded requires further tuning of the import properties.
Otherwise, the VDB may have what it needs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)