[
https://issues.apache.org/jira/browse/FLINK-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521092#comment-16521092
]
ASF GitHub Bot commented on FLINK-9642:
---------------------------------------
GitHub user Aitozi opened a pull request:
https://github.com/apache/flink/pull/6205
[FLINK-9642]Reduce the count to deal with state during a CEP process
## What is the purpose of the change
With the rework of sharedBuffer Flink-9418, the lock & release operation is
deal with state backend which is different from the previous version which will
read the state of sharedBuffer all to memory, i think we can add a cache or
variable in sharedbuffer to cache the LockAble Object to mark the ref change in
once process in NFA, this will reduce the count when the events point to the
same Node. And flush the result to MapState at the end of process.
## Brief change log
- add the eventsBufferCache and entryCache
- flush the cache after one turn process
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Aitozi/flink onceQueryCache
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/6205.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6205
----
commit 184ec24474ee5b8a1c9f932286ef4aed4f1dabd6
Author: minwenjun <minwenjun@...>
Date: 2018-06-23T12:56:55Z
[FLINK-9642]Reduce the count to deal with state during a CEP process
----
> Reduce the count to deal with state during a CEP process
> ---------------------------------------------------------
>
> Key: FLINK-9642
> URL: https://issues.apache.org/jira/browse/FLINK-9642
> Project: Flink
> Issue Type: Improvement
> Components: CEP
> Affects Versions: 1.6.0
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
> Labels: pull-request-available
>
> With the rework of sharedBuffer Flink-9418, the lock & release operation is
> deal with rocksdb state which is different from the previous version which
> will read the state of sharedBuffer all to memory, i think we can add a cache
> or variable in sharedbuffer to cache the LockAble Object to mark the ref
> change in once process in NFA, this will reduce the count when the events
> point to the same NodeId.. And flush the result to MapState at the end of
> process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
