[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2439.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Import from JSON error not helpful
> ----------------------------------
>
> Key: TEIIDDES-2439
> URL: https://issues.jboss.org/browse/TEIIDDES-2439
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
>
> When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 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 closed TEIIDDES-2440.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> 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
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 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.15#6346)
9 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 reopened TEIIDDES-2440:
--------------------------------------
Reopening to set label
> 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, 8.6.2 Beta1, 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.15#6346)
9 years