[
https://issues.apache.org/jira/browse/FLINK-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064433#comment-16064433
]
Kostas Kloudas commented on FLINK-6939:
---------------------------------------
Hi [~jark], I commented on https://issues.apache.org/jira/browse/FLINK-6983. I
totally agree with you that not storing the conditions is related to not
storing the states. This is why I said earlier that I would like to have a look
on the other PR that does not store the states, in order to come up with a plan
for not storing the conditions.
I reviewed that PR and I left some comments there. But for the issues
themselves, they seem like optimizations. So, given that they may affect the
design of future features planned for the CEP library, I suggest to leave them
for now, until we have a clear idea on how to do it. This does not seem to
affect the effort of integrating CEP with SQL.
So making the IterativeConditions rich can be done in a separate PR than the
conditionRegistry.
> 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)
