[
https://issues.apache.org/jira/browse/FLINK-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
aitozi updated FLINK-9507:
--------------------------
Description:
When we use the cep to describe a condition about the events that has been
matched, we have to call the method "getEventsForPattern" to extract the
partly matched elements from the sharedBuffer in RocksDB, which is very cost, I
think we can introduce a ReduceFunction on the pattern desc to allow us to
aggregate the value in advance. Is this practical ？ What's your guys opinion?
[~kkl0u] [~dawidwys]
was:
When we use the cep to describe a condition about the events that has been
matched, we have to call the method {code:java}getEventsForPattern{code} to
extract the partly matched elements from the sharedBuffer in RocksDB, which is
very cost, I think we can introduce a ReduceFunction on the pattern desc to
allow us to aggregate the value in advance. Is this practical ？ What's your
guys opinion? [~kkl0u] [~dawidwys]
> Introduce ReduceFunction to CEP to minor the cost for IterativeCondition
> ------------------------------------------------------------------------
>
> Key: FLINK-9507
> URL: https://issues.apache.org/jira/browse/FLINK-9507
> Project: Flink
> Issue Type: Improvement
> Components: CEP
> Affects Versions: 1.5.0
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
> Fix For: 1.6.0
>
>
> When we use the cep to describe a condition about the events that has been
> matched, we have to call the method "getEventsForPattern" to extract the
> partly matched elements from the sharedBuffer in RocksDB, which is very cost,
> I think we can introduce a ReduceFunction on the pattern desc to allow us to
> aggregate the value in advance. Is this practical ？ What's your guys
> opinion? [~kkl0u] [~dawidwys]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
