[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Matej Kralik edited comment on TEIIDDES-3169 at 12/18/17 8:21 AM:
------------------------------------------------------------------
[~blafond] In my point of view, the designer should automatic add tag to the XML when the infinispan translator is set and the third option is good too when the user wants to edit the XML for some reason.
E.g. in the 'Save as VDB XML file' wizard is 'Allow Edit XML' checkbox.
was (Author: mkralik):
In my point of view, the designer should automatic add tag to the XML when the infinispan translator is set and the third option is good too when the user wants to edit the XML for some reason.
E.g. in the 'Save as VDB XML file' wizard is 'Allow Edit XML' checkbox.
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Matej Kralik commented on TEIIDDES-3169:
----------------------------------------
In my point of view, the designer should automatic add tag to the XML when the infinispan translator is set and the third option is good too when the user wants to edit the XML for some reason.
E.g. in the 'Save as VDB XML file' wizard is 'Allow Edit XML' checkbox.
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-2683) Importing Excel file using Teiid Connection does not import extension properties
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2683?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2683:
-----------------------------------
Labels: release_notes (was: )
> Importing Excel file using Teiid Connection does not import extension properties
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2683
> URL: https://issues.jboss.org/browse/TEIIDDES-2683
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 11.1, 11.1.1
>
> Attachments: excel-import-problem.mkv
>
>
> When importing an excel file using Teiid Connection, the extension properties are silently discarded. This results in invalid model, which, when deployed and queried, causes the following error in the server log:
> bq. Connector worker process failed for atomic-request=AVU37BnZoOUS.0.0.0: org.teiid.translator.TranslatorException: TEIID23007 OPTIONS property CELL_NUMBER is required and it not defined on column ROW_ID
> The DDL obtained from the server is
> {code:sql}
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> StringNum string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> CharValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> DoubleNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> BigIntegerValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '4'),
> ShortValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '5'),
> FloatNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '6'),
> ObjectValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '7'),
> IntNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '8'),
> BigDecimalValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '9'),
> LongNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '10'),
> BooleanValue boolean OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '11'),
> TimestampValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '12'),
> ByteNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '13'),
> IntKey double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '14'),
> StringKey string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '15'),
> TimeValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '16'),
> DateValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '17'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'smalla.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> {code}
> When trying to import the same DDL using the DDL import wizard, a warning dialog is shown stating that the extension properties could not be processed and the Model Extension Definition should be registered
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-2683) Importing Excel file using Teiid Connection does not import extension properties
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2683?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2683.
----------------------------------
> Importing Excel file using Teiid Connection does not import extension properties
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2683
> URL: https://issues.jboss.org/browse/TEIIDDES-2683
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 11.1, 11.1.1
>
> Attachments: excel-import-problem.mkv
>
>
> When importing an excel file using Teiid Connection, the extension properties are silently discarded. This results in invalid model, which, when deployed and queried, causes the following error in the server log:
> bq. Connector worker process failed for atomic-request=AVU37BnZoOUS.0.0.0: org.teiid.translator.TranslatorException: TEIID23007 OPTIONS property CELL_NUMBER is required and it not defined on column ROW_ID
> The DDL obtained from the server is
> {code:sql}
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> StringNum string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> CharValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> DoubleNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> BigIntegerValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '4'),
> ShortValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '5'),
> FloatNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '6'),
> ObjectValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '7'),
> IntNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '8'),
> BigDecimalValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '9'),
> LongNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '10'),
> BooleanValue boolean OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '11'),
> TimestampValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '12'),
> ByteNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '13'),
> IntKey double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '14'),
> StringKey string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '15'),
> TimeValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '16'),
> DateValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '17'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'smalla.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> {code}
> When trying to import the same DDL using the DDL import wizard, a warning dialog is shown stating that the extension properties could not be processed and the Model Extension Definition should be registered
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3133) When JDG is used as a data source, there are not translator overrides to create
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3133?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3133:
-----------------------------------
Labels: release_notes (was: )
> When JDG is used as a data source, there are not translator overrides to create
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-3133
> URL: https://issues.jboss.org/browse/TEIIDDES-3133
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes
> Fix For: 11.1.1
>
>
> In the process of creating the full workflow for materializating a view to a JDG 7 cache, Teiid Designer was made to also create the needed translator overrides when the VDB was created. However, when a JDG 7 cache is to be used as a data source, that translator override cannot be created when the VDB is created. It causes an exception in Teiid because it thinks the cache is for materialization (due to the override).
> So a change is needed, that when a JDG cache is not for materialization, but to be used as a datasource, the translator override should not be automatically created.
> Maybe (just a suggestion) when the source tables are created from the running of the JDG materialization process, they are flagged as matview type tables, so that when the VDB is created, it knows then to create the translator override. (otherwise it doesn't create the override).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3133) When JDG is used as a data source, there are not translator overrides to create
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3133?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3133.
----------------------------------
> When JDG is used as a data source, there are not translator overrides to create
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-3133
> URL: https://issues.jboss.org/browse/TEIIDDES-3133
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes
> Fix For: 11.1.1
>
>
> In the process of creating the full workflow for materializating a view to a JDG 7 cache, Teiid Designer was made to also create the needed translator overrides when the VDB was created. However, when a JDG 7 cache is to be used as a data source, that translator override cannot be created when the VDB is created. It causes an exception in Teiid because it thinks the cache is for materialization (due to the override).
> So a change is needed, that when a JDG cache is not for materialization, but to be used as a datasource, the translator override should not be automatically created.
> Maybe (just a suggestion) when the source tables are created from the running of the JDG materialization process, they are flagged as matview type tables, so that when the VDB is created, it knows then to create the translator override. (otherwise it doesn't create the override).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-3169:
---------------------------------------
[~blafond] It may take 2 of those. Hard code to check for the translator so that the check-box can be selected. Having both options will allow for the user to develop/extend their own jdg type translator and have this option. Yes, they will have to select the check box, but at least that becomes their workaround, since the default will be deselected for them.
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3169:
----------------------------------------
[~rhn-engineering-vhalbert] [~mkralik] I could do 3 things here...
1) Check for specific translator type and hard-code the DDL change
2) Add a check-box to add "NATIVE" to the source model metadata in the DDL
3) Allow users to check box for a user to "Edit XML" to add the NATIVE change or any other XML change
Thoughts?
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3169:
-----------------------------------
Fix Version/s: 11.1.2
> Missing native tag in Teiid Importer
> ------------------------------------
>
> Key: TEIIDDES-3169
> URL: https://issues.jboss.org/browse/TEIIDDES-3169
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 11.1.2
>
> Attachments: VDBcontent.png, dataSource.png, translator.png
>
>
> Teiid importer doesn't add the NATIVE tag to VDB content.
> Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...].
> I use jdg7.1-remote-cache quick start from server.
> I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error:
> {code:java}
> 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata,
> 1) Define "importer.ProtoFilePath" to read from a local .proto file.
> 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.
> 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file
> {code}
> I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months