flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From StephanEwen <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-2866] [FLINK-2888] [FLINK-2891] Fixes f...
Date Thu, 22 Oct 2015 17:14:15 GMT
GitHub user StephanEwen opened a pull request:


    [FLINK-2866] [FLINK-2888] [FLINK-2891] Fixes for various release blocking issues

    Default state value is returned as copies in key value state. To circumvent this (if ever
becomes a performance issue), one can use null as the default state and manually check/initialize
to an immutable default value.
    Window user functions have access to key/value state even window is evaluated (part 2
- pert 1 was committed by Aljoscha earlier). The main part here is a rework of the PreAggregatingWindow
tests to make them more meaningful.
    This also includes #1282 

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

    $ git pull https://github.com/StephanEwen/incubator-flink multiple_fixes

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


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

    This closes #1289
commit 0a14e9ff3c499ca339d275b5ca58bed545f71519
Author: tedyu <yuzhihong@gmail.com>
Date:   2015-10-22T02:40:21Z

    [FLINK-2866] [runtime] Eagerly close FSDataInputStream in file state handle
    This closes #1282

commit acbcc98e9cb09554b879f60af390dbb1485f03d6
Author: Stephan Ewen <sewen@apache.org>
Date:   2015-10-22T09:24:12Z

    [FLINK-2888] [streaming] State backends return copies of the default values

commit fca433e1652840c0d8c8de1c57bd988428cc6218
Author: Stephan Ewen <sewen@apache.org>
Date:   2015-10-22T16:58:29Z

    [FLINK-2891] [streaming] Set keys for key/value state in window evaluation of fast-path


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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message