]
Steven Hawkins commented on TEIIDDES-3069:
------------------------------------------
Given the behavior of Designer to leave the default length of 0, TEIID-5111 will treat
that as the default/max for index metadata. However TEIID-5112 will expect proper length
values in DDL.
For 6.4 or older branches TEIID-5111 can be pulled back if we want, but it's not a
blocker as the workaround is to simply alter the length value for affected columns in
Designer.
odata4 fails to return data on top of mongoDB view model
---------------------------------------------------------
Key: TEIIDDES-3069
URL:
https://issues.jboss.org/browse/TEIIDDES-3069
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Environment: Noticed in JDV 6.3.4
Reporter: Michael Echevarria
Assignee: Barry LaFond
Priority: Critical
Fix For: 11.2
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