[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1870:
-----------------------------------
Fix Version/s: 8.3
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1870:
-----------------------------------
Assignee: Mark Drilling
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1870:
-----------------------------------
Component/s: Extension Framework
Import/Export
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1871) NPE While using DDL based importer
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-1871:
--------------------------------------
Summary: 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
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, 6 months
[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 edited comment on TEIIDDES-1870 at 9/30/13 12:34 PM:
------------------------------------------------------------------
> and in theory the ability to arbitrarily edit extension metadata and namespaces.
Sure, that is where #3 point come in.
What I am saying is by not allowing user to not go ahead with the import, he/she can then fix the MED defined in the Designer, then redo the import. That way we are sure that none of the properties are just dropped that are really required by the translator
BTW, currently Designer does not seem to let me edit, no I can not even view the defined properties on "built-in" MED
was (Author: rareddy):
> and in theory the ability to arbitrarily edit extension metadata and namespaces.
Sure, that is where #3 point come in.
What I am saying is by not allowing user to not go ahead with the import, he/she can then fix the MED defined in the Designer, then redo the import. That way we are sure that none of the properties are just dropped that are really required by the translator
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
>
> 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, 6 months
[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:
----------------------------------------
> and in theory the ability to arbitrarily edit extension metadata and namespaces.
Sure, that is where #3 point come in.
What I am saying is by not allowing user to not go ahead with the import, he/she can then fix the MED defined in the Designer, then redo the import. That way we are sure that none of the properties are just dropped that are really required by the translator
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
>
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1870:
------------------------------------------
> fail the import process
What do you mean by fail? I wouldn't expect a hard error. Likely you would want a warning - and in theory the ability to arbitrarily edit extension metadata and namespaces.
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
>
> 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, 6 months
[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:
----------------------------------------
When generated DDL has properties like
{code}
... OPTIONS(teiid_odata:EntityType)
{code}
Instead of resolving the "teiid_odata" or asking to match with a MED defined in the Designer, currently it silently ignores all the properties that do not match. What I am asking is to fail the import process when it can not automatically match in a MED or user fails to do so.
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
>
> 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, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1870:
------------------------------------------
Can you elaborate on #2? I'm not sure that we want designer to fail. In general I'm in favor of allowing the editing/creation of any extension properties to prevent there from being any hassle with MED unless that is what the user wants.
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
>
> 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, 6 months