[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/27/15 2:58 PM:
-----------------------------------------------------------------
Committed to master: https://github.com/Teiid-Designer/teiid-designer/commit/b26bd52bd877a9600...
9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/11dbee51413c696e0...
was (Author: blafond):
Committed to master: https://github.com/Teiid-Designer/teiid-designer/commit/b26bd52bd877a9600...
> 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 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.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2456) Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2456?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2456 at 3/27/15 2:51 PM:
-----------------------------------------------------------------
commited fix to master: https://github.com/Teiid-Designer/teiid-designer/commit/cbe8400f03ceaf726...
9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/efb7230ffc574ef7a...
was (Author: blafond):
commited fix to master: https://github.com/Teiid-Designer/teiid-designer/commit/cbe8400f03ceaf726...
> Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2456
> URL: https://issues.jboss.org/browse/TEIIDDES-2456
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 9.0.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 9.1, 9.0.2 Beta1, 9.0.2
>
> Attachments: screenshot.png
>
>
> Import using Teiid Connection sometimes fails with the following error message after getting the DDL from server and clicking Next:
> {code}
> Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null"
> {code}
> Stacktrace:
> {code}
> !ENTRY org.teiid.designer.ddl.importer.ui 4 0 2015-03-23 14:58:16.966
> !MESSAGE Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null"
> !STACK 0
> java.lang.Exception: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:54)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:101)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:225)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.core.ModelEditorImpl.getModelName(ModelEditorImpl.java:4971)
> at org.teiid.designer.relational.model.RelationalReferenceFactory.createRelationalModel(RelationalReferenceFactory.java:65)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:188)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:117)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:41)
> ... 3 more
> {code}
> (02:50:28 PM) blafond: I'll need a stack trace to figure it out
> (02:50:35 PM) blafond: check Designer's Error Log view?
> (02:50:39 PM) asmigala: the weird thing is, it sometimes works for the same data source
> (02:50:42 PM) asmigala: ok, hang on a sec
> (02:50:53 PM) asmigala: so this is not something we know about?
> (02:51:34 PM) blafond: not as a reproduceable bug.
> ...
> (02:59:47 PM) asmigala: also, when I copy the DDL, save it to a file and then use the DDL importer, it works correctlu
> 03:05:15 PM) blafond: I think it's a threading/timing issue. The RelationalReferenceFactory is assuming that the new EMF Model already created. Looks like it's still in the process "sometimes" and ends up failing.
> (03:05:45 PM) blafond: I noticed that we don't save the model right after we create it. Maybe that could fix the issue.
> (03:06:05 PM) blafond: Please log a JIRA/BZ and include all of this conversation
> (03:06:59 PM) asmigala: yes, that makes sense, I generally don't see it when stepping through the test
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months