[JBoss JIRA] (TEIIDDES-2444) Import flat file via remote URL problem
by Jan Stastny (JIRA)
Jan Stastny created TEIIDDES-2444:
-------------------------------------
Summary: Import flat file via remote URL problem
Key: TEIIDDES-2444
URL: https://issues.jboss.org/browse/TEIIDDES-2444
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.6.1
Reporter: Jan Stastny
When importing flat file via remote URL the import can't be finished. It gets stuck on screen 'Flat File Delimited Columns Parser Settings' where the 'next' button is enabled, but nothing happens after clicking it.
I encountered the issue while performing this test script: https://mojo.redhat.com/docs/DOC-1016720
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2440:
------------------------------------------
[~blafond] this is almost exactly what I had in mind, but could you please modify the message to include the suggestion to use the Properties view?
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Assignee: Barry LaFond
> Fix For: 9.1, 9.0.2, 8.6.2
>
> Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2440:
--------------------------------------
Assignee: Barry LaFond
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Assignee: Barry LaFond
> Fix For: 9.1, 9.0.2, 8.6.2
>
> Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2440:
-----------------------------------
Fix Version/s: 9.1
9.0.2
8.6.2
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Fix For: 9.1, 9.0.2, 8.6.2
>
> Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2440:
-----------------------------------
Attachment: property-not-supported.png
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2440 at 3/3/15 8:20 AM:
----------------------------------------------------------------
[~asmigala] you are correct. The issue affects multiple properties in the Table Editor.
Setting specific Table Editor row properties to read-only would be pretty difficult and probably confuse the user.
But... I do have a fix that detects when the Table Editor is being used and replaces the Cell Editor dialog with a Message Dialog stating that the editing this particular property is NOT SUPPORTED in the table editor and user should use the Properties View instead. The dialog includes the property name and target object. (See attached)
was (Author: blafond):
[~asigmala] you are correct. The issue affects multiple properties in the Table Editor.
Setting specific Table Editor row properties to read-only would be pretty difficult and probably confuse the user.
But... I do have a fix that detects when the Table Editor is being used and replaces the Cell Editor dialog with a Message Dialog stating that the editing this particular property is NOT SUPPORTED in the table editor and user should use the Properties View instead. The dialog includes the property name and target object. (See attached)
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2440:
----------------------------------------
[~asigmala] you are correct. The issue affects multiple properties in the Table Editor.
Setting specific Table Editor row properties to read-only would be pretty difficult and probably confuse the user.
But... I do have a fix that detects when the Table Editor is being used and replaces the Cell Editor dialog with a Message Dialog stating that the editing this particular property is NOT SUPPORTED in the table editor and user should use the Properties View instead. The dialog includes the property name and target object. (See attached)
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Attachments: TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2331) Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2331:
----------------------------------------
verified with TD 8.6.1.CR1
> Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)
> -------------------------------------------------------------------
>
> Key: TEIIDDES-2331
> URL: https://issues.jboss.org/browse/TEIIDDES-2331
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.4, 8.6
> Environment: Windows 7
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.0, 8.6.1, 9.0.1
>
> Attachments: Dataroles_project.zip, log.log, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png
>
>
> There is couple of issues with renaming source model that is referenced in some view model.
> I am using project Dataroles_project.zip (attached)
> 1. I tried to rename Products_source.xmi to Products_source1.xmi
> * this generates some error in log but it works...
> *[screenshot1.png]
> 2. Rename Products_source1.xmi to Products_source2.xmi
> * this fails to rewrite the reference in view model
> * I changed the references manually
> *[screenshot2.png and screenshot3.png]
> 3. Remane Products_source2.xmi to Products_source3.xmi
> * this deletes tables from view model
> *[screenshot4.png and screenshot5.png]
> This problem occurs only on Windows, Linux is fine...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (TEIIDDES-2443) Cannot paste using Ctrl+V in Transformation Editor
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2443?page=com.atlassian.jira.plu... ]
Andrej Šmigala updated TEIIDDES-2443:
-------------------------------------
Summary: Cannot paste using Ctrl+V in Transformation Editor (was: Cannot paste using Ctrl+C in Transformation Editor)
> Cannot paste using Ctrl+V in Transformation Editor
> --------------------------------------------------
>
> Key: TEIIDDES-2443
> URL: https://issues.jboss.org/browse/TEIIDDES-2443
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors, Transformations
> Affects Versions: 8.6.1
> Environment: JBDS 7.1.1
> Designer 8.6.1.CR1
> Windows, Linux
> Reporter: Andrej Šmigala
>
> When hitting Ctrl+C in the Transformation Editor, nothing happens. Right-clicking and selecting Paste works as expected.
> Probably result of fixing TEIIDDES-2348 (which happened with JBDS 8, this one is with JBDS 7).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years