[
https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-3033:
------------------------------------
The dynamic case for mode shape was really never used. Designer didn't allow you to
use the Teiid Connection Importer, had to use the jdbc importer. And at this point, it
hasn't been enabled. I was hoping to do what was planned, and that was move away
from the JDBC importer to Teiid Connection importer. So I can't recommend enabling
it, because of this issue.
As for the change, just duplicate the JDBCMetadataProcessor for the
ModeShapeMetadataProcessor and make the change only for mode shape. No need to impact any
other translator. This is really specific to mode shape.
Importing metadata thru Designer versus using dynamic VDB is
different
----------------------------------------------------------------------
Key: TEIID-3033
URL:
https://issues.jboss.org/browse/TEIID-3033
Project: Teiid
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.7.1, 8.9
Reporter: Van Halbert
Assignee: Van Halbert
The columns names and NIS, imported via Designer, show that the column name is set as the
NIS, and then converted (replace colon with underscore) to be used as the column name.
However, in the mode shape translator, this logic isn't being applied
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)