[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1870:
----------------------------------------
EntityAlias is dropped, please remove it
Here are the property extensions
# LinkTables - String/optional - On Table
# HttpMethod - String/optional - On Procedure
# JoinColumn - String/optional - on Column
# EntityType - String/optional - On Table and Procedure
# ComplexType - String/optional - On Column
# ColumnGroup - String/optional - on Column
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1870:
-----------------------------------------
We currently have in the Designer OData Med 'EntityAlias' and 'EntityType' - which are allowable ext properties of BaseTables.
1) 'EntityAlias' is not in your list - should it be removed?
2) What object type(s) can the other properties in your list extend? Columns?
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1870:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1012634
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1871) NPE While using DDL based importer
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1871?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1871:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1012634
> NPE While using DDL based importer
> ----------------------------------
>
> Key: TEIIDDES-1871
> URL: https://issues.jboss.org/browse/TEIIDDES-1871
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Attachments: sap-flight.ddl
>
>
> While importing the OData translator based DDL, encountered the below NPE.
> {code}
> Caused by: java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:117)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:330)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:453)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:362)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:195)
> at org.modeshape.sequencer.ddl.dialect.teiid.TeiidDdlParser.parseNextStatement(TeiidDdlParser.java:150)
> at org.modeshape.sequencer.ddl.StandardDdlParser.parse(StandardDdlParser.java:209)
> at org.modeshape.sequencer.ddl.DdlParsers.parseUsing(DdlParsers.java:152)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:134)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:106)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:90)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:222)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months