[teiid-issues] [JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

Steven Hawkins (JIRA) issues at jboss.org
Wed Mar 29 13:27:00 EDT 2017


    [ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13386160#comment-13386160 ] 

Steven Hawkins commented on TEIID-4829:
---------------------------------------

I meant the workaround for odata4 of setting the column lengths to something other than 0.  

> Whats odd is that odata4 is the only thing checking that length. jdbc, preview and odata2 had no issue with the zero length

That's due to the olingo library used for odata4.  Most of the other paths treat the metadata facets as informational and not something that they have to enforce.

>  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)


More information about the teiid-issues mailing list