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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on CAMEL-13082:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jan/19 16:21
            Start Date: 18/Jan/19 16:21
    Worklog Time Spent: 10m 
      Work Description: phantomjinx commented on pull request #2720: CAMEL-13082: Filter results already seen by the Olingo4 consumer
URL: https://github.com/apache/camel/pull/2720
 
 
   * Olingo4Configuration
    * Adds filterAlreadySeen property
    * Added here rather than to the endpoint as the latter would require
      ultimately, in order to satisfy various checks, changes to the
      endpoint read() method in the api's Olingo4AppImpl, which is
      unnecessary since this is used by the consumer.
   
   * Olingo4Endpoint
    * Adds filterAlreadySeen property names to the property names collection
      so that parseQueryParams() does not remove it.
    * Adds the filterAlreadySeen property during interceptProperties() in a
      just-in-time manner (avoiding possibility of it causing problems with
      endpoint and consumer initialisation).
   
   * Olingo4Consumer
    * Adds a resultIndex for indexing hashcodes of existing results
    * On receiving a response, if the resultIndex has been initialised then
      the response results are checked by getting their hashcodes. If they're
      in the resultIndex then they are discarded.
    * Prior to any polling interceptProperties is called and if the properties
      contain the filterAlreadySeen property then the resultIndex is initialised.
    * Once the results have been placed in the exchange, interceptResult() is
      called and some housekeeping is done to index all the results in the
      resultIndex ready for checking on the next polling.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 186953)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>          Time Spent: 10m
>  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)