[
https://issues.apache.org/jira/browse/FLINK-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058929#comment-16058929
]
ASF GitHub Bot commented on FLINK-6938:
---------------------------------------
Github user dianfu commented on the issue:
https://github.com/apache/flink/pull/4145
@dawidwys In my mind, to achieve `translating them to newly constructed
graph of states`, we only need to get the state from the NFA by the `state
name` stored in `ComputationState`. Not sure if my understanding is correct?
For `dynamically providing new Patterns`, do you mean dynamically changing
the NFA? Another approach coming into my mind is that we can store the states
in another `ValueState`(compared with the partially matched events stored) and
only update it if the NFA changes. What's your thought?
> IterativeCondition should support RichFunction interface
> --------------------------------------------------------
>
> Key: FLINK-6938
> URL: https://issues.apache.org/jira/browse/FLINK-6938
> Project: Flink
> Issue Type: Sub-task
> Components: CEP
> Reporter: Jark Wu
> Assignee: Jark Wu
> Fix For: 1.4.0
>
>
> In FLIP-20, we need IterativeCondition to support an {{open()}} method to
> compile the generated code once. We do not want to insert a if condition in
> the {{filter()}} method. So I suggest make IterativeCondition support
> {{RichFunction}} interface.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
