[
https://issues.apache.org/jira/browse/APEXMALHAR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354682#comment-15354682
]
Bhupesh Chawda commented on APEXMALHAR-2129:
--------------------------------------------
The current implementation advances the "start" and "end" automatically every
window by the length of a bucket span.
In case of deduplication for a data set which is not based on the current
system time (say an year old data), this is not needed. We just need to advance
"start" and "end" based on the tuple times, not automatically every window.
The idea is to decouple advancement of windows and purging. Purging will still
happen, just not with the default "lowestTimeBucket" which is incremented by 1
every window.
> Introduce option to advance time through Expiry task in TimeBucketAssigner
> --------------------------------------------------------------------------
>
> Key: APEXMALHAR-2129
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2129
> Project: Apache Apex Malhar
> Issue Type: Task
> Reporter: Bhupesh Chawda
> Assignee: Bhupesh Chawda
> Priority: Minor
>
> TimeBucketAssigner advances the time boundaries of the buckets viz. start and
> end to the current system time every window.
> The requirement is to add an option so that clients can disable this if
> needed. Tuple time based deduplication has such a requirement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
