[teiid-issues] [JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model
[
https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4829:
---------------------------------------
That's showing a length of 0 for the affected columns. Ideally it would trigger a
metadata error in Designer, as that is not expected.
The runtime is effectively honoring that in the odata layer by indicating that the values
are too long. If you increase the length property to a wide enough value, the odata 4
path should work.
So the follow on tasks may be here:
- determine if a designer validation is needed
- determine what set the length to 0 initially. How was the mongodb metadata created?
odata4 fails to return data on top of mongoDB view model
---------------------------------------------------------
Key: TEIID-4829
URL: https://issues.jboss.org/browse/TEIID-4829
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.9.6_3
Environment: Noticed in JDV 6.3.4
Reporter: Michael Echevarria
Assignee: Steven Hawkins
Priority: Critical
Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28
15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28
15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png
Description of problem:
Accessing either an exclusive view model or combined view model for a mongoDB datasource
via odata4 results in an error.
The data returns via odata2, jdbc and preview in the designer
Version-Release number of selected component (if applicable):
JDV 6.3.4
Actual results:
Property mapping error
Expected results:
Model data
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)