[
https://issues.apache.org/jira/browse/FLINK-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943411#comment-15943411
]
ASF GitHub Bot commented on FLINK-6197:
---------------------------------------
GitHub user kl0u opened a pull request:
https://github.com/apache/flink/pull/3624
[FLINK-6197] [cep] Add support for iterative conditions.
So far, the where clause only supported simple FilterFunction
conditions. With this, we add support for conditions where an
event is accepted not only based on its own properties, e.g.
name, as it was before, but also based on some statistic
computed over previously accepted events in the pattern, e.g.
if the price is higher than the average of the prices of the
previously accepted events.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kl0u/flink cep-iterative-functions
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3624.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 #3624
----
commit dfb848b83864071ef6738261e425bf4d0e43575d
Author: kl0u <[email protected]>
Date: 2017-03-22T14:52:07Z
[FLINK-6197] [cep] Add support for iterative conditions.
So far, the where clause only supported simple FilterFunction
conditions. With this, we add support for conditions where an
event is accepted not only based on its own properties, e.g.
name, as it was before, but also based on some statistic
computed over previously accepted events in the pattern, e.g.
if the price is higher than the average of the prices of the
previously accepted events.
----
> Add support for iterative conditions.
> -------------------------------------
>
> Key: FLINK-6197
> URL: https://issues.apache.org/jira/browse/FLINK-6197
> Project: Flink
> Issue Type: Bug
> Components: CEP
> Affects Versions: 1.3.0
> Reporter: Kostas Kloudas
> Assignee: Kostas Kloudas
> Fix For: 1.3.0
>
>
> So far, the {{where}} clause only supported simple {{FilterFunction}}
> conditions.
> With this, we want to add support for conditions where the an event is
> accepted not only based on its own properties, e.g. name, as it was before,
> but also based on some statistic computed over previously accepted events in
> the pattern, e.g. if the price is higher than the average of the prices of
> the previously accepted events.
> This in combination with the recently added quantifiers will allow for a lot
> more expressive patterns.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
