[
https://issues.apache.org/jira/browse/FLINK-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062508#comment-16062508
]
Jark Wu commented on FLINK-6939:
--------------------------------
Hi [~kkl0u], thanks for your response. The purpose of this issue is that, in
order to integrate CEP and SQL, an important step is code generation of
IterativeCondition and compile it in runtime. But the conditions are
de/serialized on every input elements, so that we have to compile the code on
every input elements which is not we want. We hope to compile the code only in
the setup phase of CEP operator. In order to achieve this goal, we should not
store conditions with NFA states.
I think store conditions upon creation of the NFA is a good idea. And
[~dian.fu] and [~Dawid Wysakowicz had a discussion about this last week.
Storing NFA meta data (I think it should include conditions) separately with
NFA states. See FLINK-6983
> Not store IterativeCondition with NFA state
> -------------------------------------------
>
> Key: FLINK-6939
> URL: https://issues.apache.org/jira/browse/FLINK-6939
> Project: Flink
> Issue Type: Sub-task
> Components: CEP
> Reporter: Jark Wu
> Assignee: Jark Wu
> Fix For: 1.4.0
>
>
> Currently, the IterativeCondition is stored with the total NFA state. And
> de/serialized every time when update/get the NFA state. It is a heavy
> operation and not necessary. In addition it is a required feature for
> FLINK-6938.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
