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

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

GitHub user davidyan74 opened a pull request:

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

    APEXMALHAR-2305 #resolve Mirror the proto-session window behavior des…

    …cribed in the streaming 102 blog
    
    @siyuanh  please review and merge

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

    $ git pull https://github.com/davidyan74/apex-malhar APEXMALHAR-2305

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

    https://github.com/apache/apex-malhar/pull/458.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 #458
    
----
commit 0e598eba46fc39e706eda2ff9a7eedd1c8b0f2de
Author: David Yan <da...@datatorrent.com>
Date:   2016-10-18T22:41:28Z

    APEXMALHAR-2305 #resolve Mirror the proto-session window behavior described 
in the streaming 102 blog

----


> Change implementation of session window to reflect what is described in 
> streaming 102 blog
> ------------------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2305
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2305
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: David Yan
>            Assignee: David Yan
>
> The proto-session windows described in the streaming 102 blog have a minimum 
> duration that is equal to the session gap. We should do the same in our 
> session window implementation. 
> https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-102



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to