GitHub user sjwiesman opened a pull request:

    https://github.com/apache/flink/pull/3479

    [FLINK-5929] Allow Access to Per-Window State in ProcessWindowFunction

    Right now, the state that a WindowFunction or ProcessWindowFunction can
    access is scoped to the key of the window but not the window itself.
    That is, state is global across all windows for a given key.
    For some use cases it is beneficial to keep state scoped to a window.
    For example, if you expect to have several Trigger firings (due to early
    and late firings) a user can keep state per window to keep some
    information between those firings.
    
    
    @aljoscha 

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

    $ git pull https://github.com/sjwiesman/flink FLINK-5929

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

    https://github.com/apache/flink/pull/3479.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 #3479
    
----
commit 623edd1fb107e8dd0aae755a7b252df1f91713bd
Author: Seth Wiesman <[email protected]>
Date:   2017-03-06T04:07:18Z

    [FLINK-5929] Allow Access to Per-Window State in ProcessWindowFunction
    
    Right now, the state that a WindowFunction or ProcessWindowFunction can
    access is scoped to the key of the window but not the window itself.
    That is, state is global across all windows for a given key.
    For some use cases it is beneficial to keep state scoped to a window.
    For example, if you expect to have several Trigger firings (due to early
    and late firings) a user can keep state per window to keep some
    information between those firings.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to