[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418173#comment-15418173
 ] 

ASF GitHub Bot commented on APEXMALHAR-2129:
--------------------------------------------

GitHub user chandnisingh reopened a pull request:

    https://github.com/apache/apex-malhar/pull/366

    APEXMALHAR-2129 removed moving time boundaries periodically and async…

    …hrnously based on system time

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chandnisingh/apex-malhar APEXMALHAR-2129

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/apex-malhar/pull/366.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #366
    
----
commit bd5cdfe075be148da644f2faf2a9c8123a31dfdc
Author: Chandni Singh <[email protected]>
Date:   2016-08-10T21:09:30Z

    APEXMALHAR-2129 removed moving time boundaries periodically and 
asynchrnously based on system time

----


> 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.
> 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)

Reply via email to