[
https://issues.apache.org/jira/browse/FLINK-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882637#comment-15882637
]
ASF GitHub Bot commented on FLINK-5420:
---------------------------------------
GitHub user kl0u opened a pull request:
https://github.com/apache/flink/pull/3412
[FLINK-5420] [cep] Make the CEP operators rescalable
More on the related JIRA: https://issues.apache.org/jira/browse/FLINK-5420
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kl0u/flink cep-uni-rescale
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3412.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 #3412
----
commit ee5862973d2b8b8dca8333eaaff6ca82a4e9a069
Author: kl0u <[email protected]>
Date: 2017-02-24T09:34:43Z
[FLINK-5420] [cep] Make the CEP operators rescalable
Introduces the KeyRegistry in the TimeServiceHandler
which allows to specify a callback and register keys
for which we want this callback to be invoked on each
watermark.
Given this service, now the CEP operator has only
keyed state, and the non-keyed one (keys) are
handled by the KeyRegistry.
----
> Make CEP operators rescalable
> -----------------------------
>
> Key: FLINK-5420
> URL: https://issues.apache.org/jira/browse/FLINK-5420
> Project: Flink
> Issue Type: Bug
> Components: CEP
> Affects Versions: 1.2.0
> Reporter: Kostas Kloudas
> Assignee: Kostas Kloudas
>
> This issue targets making the operators in the CEP library re-scalable. After
> this is implemented, the user will be able to take a savepoint and restart
> his job with a different parallelism.
> This issue depends on https://issues.apache.org/jira/browse/FLINK-5845.
> The way this is done is that we introduce the {{TimeServiceHandler}} in the
> {{AbstractStreamOperator}}, which keeps the registered
> {{InternalTimerService}} s (before this was in the
> {{AbstractStreamOperator}}) and a new service called {{KeyRegistry}}. The
> {{KeyRegistry}} will be fault tolerant and rescalable and will allow to
> register keys and a callback which will be invoked for each registered key
> upon reception of a watermark. This can be seen as keeping (recurring) timers
> for each of the registered keys that will fire "at the next watermark".
> After introducing this service, upon reception of a watermark, all the
> processing of the NFAs will be delegated to the callback.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
