[
https://issues.apache.org/jira/browse/FLINK-7293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106909#comment-16106909
]
Dian Fu edited comment on FLINK-7293 at 7/31/17 7:35 AM:
---------------------------------------------------------
Agree that we can sort both by the time and the custom order by in the upstream
and then forward the results to CEP. While I still think that having a custom
sort logic in CEP is very important. This would give users who use CEP API more
flexibility to control the order of the matching events. As for CEP, the order
of the events is very important. Without this feature, the matched results will
be non-deterministic for many use case.
was (Author: dian.fu):
Agree that we can sort both by the time and the custom order by in the upstream
and then forward the results to CEP. While I still think that having a custom
sort logic in CEP is very important. This would give users who use CEP API more
flexibility to control the order of the matching events. As for CEP, the order
of the events is very important, without this feature, the matched results will
be non-deterministic for many use case.
> Support custom order by in PatternStream
> ----------------------------------------
>
> Key: FLINK-7293
> URL: https://issues.apache.org/jira/browse/FLINK-7293
> Project: Flink
> Issue Type: Sub-task
> Components: CEP
> Reporter: Dian Fu
> Assignee: Dian Fu
>
> Currently, when {{ProcessingTime}} is configured, the events are fed to NFA
> in the order of the arriving time and when {{EventTime}} is configured, the
> events are fed to NFA in the order of the event time. It should also allow
> custom {{order by}} to allow users to define the order of the events besides
> the above factors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
