[JBoss JIRA] (TEIIDDES-2774) Cannot extract model from imported VDB with same name
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2774?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2774:
------------------------------------------
[~blafond] yes, but the attached patch is for TEIIDDES-2769 and concerns dataroles in vdb.
> Cannot extract model from imported VDB with same name
> -----------------------------------------------------
>
> Key: TEIIDDES-2774
> URL: https://issues.jboss.org/browse/TEIIDDES-2774
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Attachments: extract_model.vdb, org.teiid.designer.vdb-TEIIDDES-2769.patch
>
>
> After importing a VDB, the extract model Quick FIx is not available if the model has the same name as the VDB. Designer considers the VDB to be the same as the model, and offers to "synchronize" to model (which does nothing).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2758) Change interger type to biginterger/int after import
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2758?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2758:
----------------------------------------
[~mmakovy] The virtual doc/views have a BigInteger : integer defined. The runtime type *integer* equates to a *long* at design-time. Should *integer* be converted to *long*?
> Change interger type to biginterger/int after import
> ----------------------------------------------------
>
> Key: TEIIDDES-2758
> URL: https://issues.jboss.org/browse/TEIIDDES-2758
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Attachments: QT_MySql50_Push.vdb
>
>
> Integer type was removed. After importing older VDB, TD complains about type incompatibility. Is there a possibility to check for integer in models after import and change it to biginterger/int?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2774) Cannot extract model from imported VDB with same name
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2774?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2774:
----------------------------------------
[~asmigala] nope. Already have a fix. Basically we weren't checking if target resource was actually the VDB, so added file extension checks.
> Cannot extract model from imported VDB with same name
> -----------------------------------------------------
>
> Key: TEIIDDES-2774
> URL: https://issues.jboss.org/browse/TEIIDDES-2774
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Attachments: extract_model.vdb, org.teiid.designer.vdb-TEIIDDES-2769.patch
>
>
> After importing a VDB, the extract model Quick FIx is not available if the model has the same name as the VDB. Designer considers the VDB to be the same as the model, and offers to "synchronize" to model (which does nothing).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2759) Missing translator after import
by Barry LaFond (JIRA)
[ 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)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2774) Cannot extract model from imported VDB with same name
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2774?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2774:
------------------------------------------
[~blafond], you probably attached the patch to the wrong issue by mistake
> Cannot extract model from imported VDB with same name
> -----------------------------------------------------
>
> Key: TEIIDDES-2774
> URL: https://issues.jboss.org/browse/TEIIDDES-2774
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Attachments: extract_model.vdb, org.teiid.designer.vdb-TEIIDDES-2769.patch
>
>
> After importing a VDB, the extract model Quick FIx is not available if the model has the same name as the VDB. Designer considers the VDB to be the same as the model, and offers to "synchronize" to model (which does nothing).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months