[JBoss JIRA] (TEIIDDES-2683) Importing Excel file using Teiid Connection does not import extension properties
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2683?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2683:
-----------------------------------
Fix Version/s: 9.0.7
> 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
> Fix For: 9.0.7
>
>
> 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
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2834:
----------------------------------------
Wish our workflow was easier, but Designer is stuck with Eclipse, EMF and INDEXED metadata files. All of those really manage the "workspace/project" models and associated INDEX files. A VDB is just a snapshot of these files plus user-defined data roles and customized properties. Applying *VDB* properties between VDBs wouldn't be a hard feature to add. Migrating Data roles would be difficult because these roles reference specific models, tables, columns and views.
Our longer term goal is to get all of this right with our new Teiid Tooling which leverages the our Komodo Engine/Editor backed by a Modeshape JCR.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Steve Tran commented on TEIIDDES-2834:
--------------------------------------
Actually, building the VDB is easy part. I just need to select which layers I want to include, so maybe the workaround is to just delete your VDB and build it over again. As long as I don't have to rebuild all my XMI files (by the refresh the SQL trick), then it should be okay.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Steve Tran commented on TEIIDDES-2834:
--------------------------------------
No, I didn't check in the .project files or any of the Eclipse metadata. Typically, when I check out any project from GIT, the folder that I check it out into doesn't matter because all the files inside of it never reference anything absolutely. It's usually ../../xyz for example.
I'm in a weird situation now because I created a VDB project in a folder called steve_project. In the VDB file, there are references to "steve_project" as the root folder. I've committed this work into GIT under a repo that may or may not have the same name. In this case, it's called VDB_Project1. When someone else comes and clones VDB_Project1, the name that they name their local folder on their system MUST be "steve_project", or else all the internal references are broken.
I fully agree with you that hand editing any of these generated VDB files/xml is hacky. As it turns out, my workaround leads to an undeployable VDB, so it looks like everyone will need to use "steve_project" as their project folder from now on.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2834:
----------------------------------------
[~sqtran] The Model Project name is an Eclipse resource name and probably shouldn't be used as a GIT repo name. On the one hand it makes sense for simplicity-sake, but in this case, your repo will be containing an eclipse ".project" and other eclipse project-related files. For development, typically Ecilpse and/or Maven plugins, for instance, are contained within a parent folder in a repo. Any chance you could adopt at least one more layer in each repo to maintain this eclipse project integrity?
Note also the Teiid VDB archive contains XMI files which are not deployed as runtime metadata. That metadata is included in the VDB via 1234567890.INDEX files. 1 per model. The vdb.xml also contains checksum values for each model to use for determining "sychronization". The may be one of the reasons you have to force/edit the view model & save and force re-synch. The vdb.xml also has a backing schema... so in the end, hand-editing the vdb.xml file is not recommended.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Steve Tran commented on TEIIDDES-2834:
--------------------------------------
Correct.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2834:
----------------------------------------
[~sqtran] Trying to understand your work-flow. So are you defining each "Teiid Model Project" in it's own git repo?
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Steve Tran commented on TEIIDDES-2834:
--------------------------------------
Yes correct. I spent about an hour and figured out a workaround. It involves opening up your VDB and manually editing the vdb.xml file. Replace the old project root with the new project root and it'll pick up the XMI locations correctly.
The XMI files themselves seemed to be out of sync though. The workaround for that is opening each XMI file up and forcing Designer to refresh the model. This can be accomplished by "editing" the transformation SQL (by adding a space or something to register a change) and saving the file. So far it looks ok but I will test further and see what happens.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2834:
----------------------------------------
Basically then the XMI files are using absolute paths, or relative path including the project name, you want that to be relative path to project's root.
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-4174 to TEIIDDES-2834:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2834 (was: TEIID-4174)
> Local project name baked into VDB
> ---------------------------------
>
> Key: TEIIDDES-2834
> URL: https://issues.jboss.org/browse/TEIIDDES-2834
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
>
> With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to.
> I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years