[
https://issues.apache.org/jira/browse/CAMEL-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754854#comment-16754854
]
Dmitry Volodin commented on CAMEL-13082:
----------------------------------------
[~phantomjinx], it's a very nice work to add filter already polled results
capabilities to the camel-olingo4 component, but I think, that in cloud
environment with multiple scaled pod or containers with the same consumer route
we will get unpredictable results (much better that without filter but still
not consistent). What do you think about to add distributed cache capabilities
to Olingo4Index?
Or restrict such containers with singleton is possible solution (will add to
camel docs and/or need to be restricted in syndesis project).
> 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-olingo2, camel-olingo4
> Affects Versions: 2.21.0, 2.23.0
> Reporter: Paul Richardson
> Assignee: Dmitry Volodin
> Priority: Major
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
