[
https://issues.jboss.org/browse/TEIIDDES-2759?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2759:
----------------------------------------
This VDB was created prior to model extension framework, so extracting the models will not
inject the built-in MEDs into them. So the translator name defined in the VDB has no
reference in the included model.
If user performs "Set Translator" on the source, the MEDs will be injected and
the translator correctly set.
We could possibly auto-inject the translator name, but any of the other connection info
used to create/import the source model won't be available (connection profile).
An old model project may also be migrated, so adding validation and quick fixes for the
also makes sense, so this is probably a piece of a larger migration feature set.
Missing translator after import
-------------------------------
Key: TEIIDDES-2759
URL:
https://issues.jboss.org/browse/TEIIDDES-2759
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 9.0.4
Reporter: Matus Makovy
Attachments: QT_MySql50_Push.vdb
Imported VDB has 2 Source models, one of them is missing a translator after import.
Translator is specified in original vdb.xml included in TD vdb.
{code:xml}
<model visible="true" type="PHYSICAL" name="SP"
path="/BQT_MySql/SP.xmi">
<property value="64600437" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="2822882286.INDEX" name="indexName"/>
<source translator-name="mysql5"
connection-jndi-name="MySQL50_PushDS" name="SP"/>
<validation-error path="sp_rows_between/ResultSet/BigIntegerValue"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error path="sp_all_smalla_rows/ResultSet/DoubleNum"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error path="sp_rows_between/ResultSet/BigDecimalValue"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error
path="sp_all_smalla_rows/ResultSet/BigDecimalValue"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error path="sp_all_smalla_rows/ResultSet/FloatNum"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error path="sp_rows_between/ResultSet/FloatNum"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error path="sp_rows_between/ResultSet/DoubleNum"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
<validation-error
path="sp_all_smalla_rows/ResultSet/BigIntegerValue"
severity="WARNING">Missing or invalid Precision on column with a numeric
datatype (See validation Preferences)</validation-error>
</model>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)