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