You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Bhupesh Chawda (JIRA)" <ji...@apache.org> on 2016/08/12 05:12:20 UTC
[jira] [Updated] (APEXMALHAR-2129) ManagedState: Disable purging
based on system time
[ https://issues.apache.org/jira/browse/APEXMALHAR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bhupesh Chawda updated APEXMALHAR-2129:
---------------------------------------
Summary: ManagedState: Disable purging based on system time (was: ManagedState: Add a disable purging option)
> ManagedState: Disable purging based on system time
> --------------------------------------------------
>
> 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
> Fix For: 3.5.0
>
>
> Have an option that can disable purging of data.
> Currently the TimeBucketAssigner moves time boundary periodically based on system time as well as based on event time. This is error prone and moving time boundary periodically implies that data will always be purged.
> The change that needs to be made to TimeBucketAssigner is to just move time boundary when there are future events that don't fall in that boundary. This will imply that if there are no events outside the current boundary then data will not be purged.
> ManagedStateImpl uses processing time for an event, so moving boundaries based on system time is going to happen there nevertheless.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)