You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (JIRA)" <ji...@apache.org> on 2017/07/28 13:06:00 UTC

[jira] [Comment Edited] (FLINK-7292) Fix EMPTY MATCH bug in CEP.

    [ https://issues.apache.org/jira/browse/FLINK-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104917#comment-16104917 ] 

Dawid Wysakowicz edited comment on FLINK-7292 at 7/28/17 1:05 PM:
------------------------------------------------------------------

I would not say it is a bug. It is a architectural choice not to return empty results. I personally don't see any value in such results. Could you show some use cases for that?


was (Author: dawidwys):
I would not say it is a bug. It is a architectural choice not to return empty results. I personally don't see any value in such results.

> Fix EMPTY MATCH bug in CEP.
> ---------------------------
>
>                 Key: FLINK-7292
>                 URL: https://issues.apache.org/jira/browse/FLINK-7292
>             Project: Flink
>          Issue Type: Bug
>          Components: CEP
>            Reporter: zhangxiaoyu
>
> Currently, with the pattern {quote}a? {quote}and the event{quote} a1{quote}, the result pattern is only {quote} {a1}{quote}, without the empty match.
> We wish the empty matched is also returned. And I am working on this issue now.
> My method is  checking if there exists empty match only when the the first event comes(at the StartState) ——try to traverse the PROCEED edges with the trueFunction condition from the StartState, see if it can arrive FinalState, if so, add an empty list to the result.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)