[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-1870) OData Importing issues
[
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