[
https://issues.apache.org/jira/browse/APEXMALHAR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415717#comment-15415717
]
Chandni Singh edited comment on APEXMALHAR-2129 at 8/10/16 6:47 PM:
--------------------------------------------------------------------
[~bhup...@apache.org]
In TimeBucketAssigner, {code}expiryTask{code} is a task that runs repeatedly to
purge data. It is not a different feature from purging.
However, I will remove this task. Right now purging is happening with a mix of
event + system time which is likely to be error prone.
It should be only triggered by events. If all the events fall between the start
and end time, then nothing will be purged. However if we see events outside
this boundary, then older time-buckets will be purged.
was (Author: csingh):
[~bhup...@apache.org]
In TimeBucketAssigner, {code}expiryTask{code} is a task that runs repeatedly to
purge data. It is not a different feature from purging.
I will rename the task, to avoid the confusion.
When purging is disabled, then you store and dedup across the entire data set.
> ManagedState: Add a disable purging option
> ------------------------------------------
>
> Key: APEXMALHAR-2129
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2129
> Project: Apache Apex Malhar
> Issue Type: Task
> Reporter: Bhupesh Chawda
> Assignee: Chandni Singh
>
> Have an option that can disable purging of data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
