[
https://issues.apache.org/jira/browse/FLINK-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058898#comment-16058898
]
ASF GitHub Bot commented on FLINK-6938:
---------------------------------------
Github user dawidwys commented on the issue:
https://github.com/apache/flink/pull/4145
@dianfu I agree that we should consider removing states from serialization,
but I have some concerns about it:
1. `State`s are part of `ComputationState`s which describe partial matches,
which means they are definitely not metadata. If we do not want to store
`State`s, I think we will be forced to either drop checkpointing of partial
matches or implement logic of translating them to newly constructed graph of
states, which I think would be hard if possible at all.
2. One feature I would like to see in FlinkCEP library is dynamically
providing new Patterns(e.g. through Side Inputs), I think in this case `State`s
serializing will be crucial.
> 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)
