[FLINK-9576] Wrong contiguity documentation

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Component/s: Documentation, Library / CEP
• Labels: pull-request-available
• Assignee: Dawid Wysakowicz
• Reporter: Dawid Wysakowicz
• Created: 13/Jun/18 13:21
• Updated: 07/Aug/18 14:03
• Resolved: 07/Aug/18 14:03

Description

Example for the contiguity is first of all wrong, and second of all misleading:

 

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.

 

Results for the relaxed contiguity are wrong plus they do not clearly explains the internal contiguity of kleene closure.

Issue Links

• links to: GitHub Pull Request #6268
• links to: GitHub Pull Request #6268