flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepak Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FLINK-9576) Wrong contiguity documentation
Date Tue, 17 Jul 2018 15:25:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Deepak Sharma reassigned FLINK-9576:
------------------------------------

    Assignee: Dawid Wysakowicz

> Wrong contiguity documentation
> ------------------------------
>
>                 Key: FLINK-9576
>                 URL: https://issues.apache.org/jira/browse/FLINK-9576
>             Project: Flink
>          Issue Type: Bug
>          Components: CEP, Documentation
>            Reporter: Dawid Wysakowicz
>            Assignee: Dawid Wysakowicz
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>
> Example for the contiguity is first of all wrong, and second of all misleading:
>  
> {code:java}
> To illustrate the above with an example, a pattern sequence "a+ b" (one or more "a"’s
followed by a "b") with input "a1", "c", "a2", "b" will have the following results:
> Strict Contiguity: {a2 b} – the "c" after "a1" causes "a1" to be discarded.
> Relaxed Contiguity: {a1 b} and {a1 a2 b} – "c" is ignored.
> Non-Deterministic Relaxed Contiguity: {a1 b}, {a2 b}, and {a1 a2 b}.
> For looping patterns (e.g. oneOrMore() and times()) the default is relaxed contiguity.
If you want strict contiguity, you have to explicitly specify it by using the consecutive()
call, and if you want non-deterministic relaxed contiguity you can use the allowCombinations()
call.
> {code}
>  
> Results for the relaxed contiguity are wrong plus they do not clearly explains the internal
contiguity of kleene closure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message