[
https://issues.apache.org/jira/browse/FLINK-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062990#comment-16062990
]
Dian Fu edited comment on FLINK-3414 at 6/26/17 12:08 PM:
----------------------------------------------------------
Hi [~dawidwys], +1 to this proposal. Restricting illegal patterns at API level
is more user friendly. The following two questions from my side:
# Why we need to port NFACompiler?
# Should we also consider the Java API?
was (Author: dian.fu):
Hi [~dawidwys], +1 to this proposal. Restricting illegal patterns at API level
is more user friendly. Two questions from my side:
# Why we need to port NFACompiler?
# Will we also consider the Java API?
> Add Scala API for CEP's pattern definition
> ------------------------------------------
>
> Key: FLINK-3414
> URL: https://issues.apache.org/jira/browse/FLINK-3414
> Project: Flink
> Issue Type: Improvement
> Components: CEP
> Affects Versions: 1.0.0
> Reporter: Till Rohrmann
> Assignee: Dawid Wysakowicz
> Priority: Minor
>
> Currently, the CEP library only supports a Java API to specify complex event
> patterns. In order to make it a bit less verbose for Scala users, it would be
> nice to also add a Scala API for the CEP library.
> A Scala API would also allow to pass Scala's anonymous functions as filter
> conditions or as a select function, for example, or to use partial functions
> to distinguish between different events.
> Furthermore, the Scala API could be designed to feel a bit more like a DSL:
> {code}
> begin "start" where _.id >= 42 -> "middle_1" as classOf[Subclass] ||
> "middle_2" where _.name equals "foobar" -> "end" where x => x.id <= x.volume
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
