You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Paul Richardson (JIRA)" <ji...@apache.org> on 2019/01/18 16:17:00 UTC

[jira] [Commented] (CAMEL-13082) Introduce an Olingo4 results-already-seen property to filter old results

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

Paul Richardson commented on CAMEL-13082:
-----------------------------------------

Despite returning an empty \{{ClientEntitySet}}, the backoffXXX properties will not idle the connection unless CAMEL-13077 is fixed first.

> Introduce an Olingo4 results-already-seen property to filter old results
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-13082
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13082
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-olingo4
>    Affects Versions: 2.21.0, 2.23.0
>            Reporter: Paul Richardson
>            Priority: Major
>
> The current polling implementation of the olingo4 consumer is to extract results from the target OData service every n seconds, with the results of each polling being identical. In the same way as the twitter component it would be useful for the consumer to recognise individual results as 'already seen' and filter them out. This has the following advantages:
>  * A set of polling results no longer contains the 'noise' of repeated results;
>  * With the possibility of all results being filtered out since they've already been seen, it is possible for the polling to idle and await new data rather than constantly returning the same results repeatedly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)