[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-1092) User shouldn't able to pick the JDBC Metadata Processor
[
https://issues.jboss.org/browse/TEIIDDES-1092?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1092:
----------------------------------------
The reason it can be changed by user is because the logic to discover the processor type
is based on current "vendor" IDs from DTP connection profiles. If Oracle, for
instance, decided to contribute a new CP and user a slightly different ID (i.e. PostgreSQL
instead of Postgres) then the importer may not find a match, but the user would know and
be able to select it.
User shouldn't able to pick the JDBC Metadata Processor
-------------------------------------------------------
Key: TEIIDDES-1092
URL: https://issues.jboss.org/browse/TEIIDDES-1092
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.4
Reporter: Randall Hauch
Attachments: Import DB metadata processor.png
Does it make sense in the "Import Database via JDBC" wizard that after setting
up or choosing an existing Connection Profile that the user can choose/change a JDBC
Metadata Processor? Seems dangerous, plus it's something else the user has to
learn/understand, or choose to ignore.
If this is intentional or is expected behavior, please feel free to close without fixing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira