GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/1195
[hotfix] Simplify new windowing API
Before, there would be three different window() methods on
KeyedDataStream: one that takes two policies, one that takes one policy
and one that takes a window assigner.
Now, there is only one window() method that takes a window assigner and
creates a KeyedWindowDataStream.
For conveniece, there are two methods timeWindows() that take either one
argument (tumbling windows) or two arguments (sliding windows). These
create a KeyedWindowDataStream with either a SlidingWindows or
TumblingWindows assigner.
When the window operator is created we pick the optimized aligned time
windows operator if the combination of window assigner/trigger/evictor
allows it.
All of this behaviour is verified in tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink simplify-windowing
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1195.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 #1195
----
commit 19e55e23470a573abbb6a874b955f6019e31eda5
Author: Aljoscha Krettek <[email protected]>
Date: 2015-09-29T18:22:11Z
[hotfix] Simplify new windowing API
Before, there would be three different window() methods on
KeyedDataStream: one that takes two policies, one that takes one policy
and one that takes a window assigner.
Now, there is only one window() method that takes a window assigner and
creates a KeyedWindowDataStream.
For conveniece, there are two methods timeWindows() that take either one
argument (tumbling windows) or two arguments (sliding windows). These
create a KeyedWindowDataStream with either a SlidingWindows or
TumblingWindows assigner.
When the window operator is created we pick the optimized aligned time
windows operator if the combination of window assigner/trigger/evictor
allows it.
All of this behaviour is verified in tests.
----
---
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.
---
