[
https://issues.apache.org/jira/browse/FLINK-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571358#comment-16571358
]
ASF GitHub Bot commented on FLINK-4636:
---------------------------------------
dawidwys commented on issue #2568: [FLINK-4636] Add boundary check for
priorityqueue for cep operator
URL: https://github.com/apache/flink/pull/2568#issuecomment-410998114
As @kl0u already mentioned this PR is very much outdated right now. Closing
this PR.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> AbstractCEPPatternOperator fails to restore state
> -------------------------------------------------
>
> Key: FLINK-4636
> URL: https://issues.apache.org/jira/browse/FLINK-4636
> Project: Flink
> Issue Type: Bug
> Components: CEP
> Affects Versions: 1.1.2, 1.2.0
> Reporter: Fabian Hueske
> Assignee: Jagadish Bihani
> Priority: Major
>
> The {{restoreState()}} of the {{AbstractCEPPatternOperator}} restores the a
> Java {{PriorityQueue}}. For that it first reads the number of elements to
> insert and then creates a {{PriorityQueue}} object. However, Java's
> {{PriorityQueue}} cannot be instantiated with an initial capacity of {{0}},
> which is not checked.
> In case of an empty queue, the {{PriorityQueue}} should be instantiated with
> an initial size of {{1}}.
> See
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Problem-with-CEPPatternOperator-when-taskmanager-is-killed-tp9024.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
