[jira] [Commented] (CAMEL-15405) Propagate inline count in Olingo2 component when using splitResults=true

["Christoph Deppisch (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-15405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176841#comment-17176841 ] 

Christoph Deppisch commented on CAMEL-15405:
--------------------------------------------

The inline count is set on the ODataFeed metadata. When split is enabled the feed gets split into its individual OData entries which becomes the new exchange body.

> Propagate inline count in Olingo2 component when using splitResults=true
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-15405
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15405
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-olingo2
>            Reporter: Christoph Deppisch
>            Priority: Major
>
> Users can query the result count as part of a search result meta data when reading entity sets from OData services (see section 4.9. Inlinecount System Query Option ($inlinecount) in [https://www.odata.org/documentation/odata-version-2-0/uri-conventions/]).
> When splitResults is enabled on the component this inline result count is not propagated to the split exchange.
> We should manually add the inline count in the same way as camel-olingo4 component is doing by adding a ResultCount property on the OData entry.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)