]
Michael Echevarria commented on TEIID-4829:
-------------------------------------------
So once I manually added a length in the properties then odata4 worked. I'm probably
going to go back and check the length on what the importer set by default for other
sources since some of them seem pretty long
!designer-length-added.png|thumbnail! !odata4-with-length-changed.png|thumbnail!
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, designer-length-added.png, mongo-view-error.png, odata2-works.png,
odata4-error.png, odata4-with-length-changed.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