dawidwys closed pull request #7380: [hotfix][docs] Fix incorrect example in cep
doc
URL: https://github.com/apache/flink/pull/7380
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/dev/libs/cep.md b/docs/dev/libs/cep.md
index ce9a9c3d72b..8c89974b6b0 100644
--- a/docs/dev/libs/cep.md
+++ b/docs/dev/libs/cep.md
@@ -1324,7 +1324,7 @@ For example, for a given pattern `b+ c` and a data stream
`b1 b2 b3 c`, the diff
</table>
Have a look also at another example to better see the difference between
NO_SKIP and SKIP_TO_FIRST:
-Pattern: `(a | c) (b | c) c+.greedy d` and sequence: `a b c1 c2 c3 d` Then the
results will be:
+Pattern: `(a | b | c) (b | c) c+.greedy d` and sequence: `a b c1 c2 c3 d` Then
the results will be:
<table class="table table-bordered">
@@ -1339,12 +1339,11 @@ Pattern: `(a | c) (b | c) c+.greedy d` and sequence: `a
b c1 c2 c3 d` Then the r
<code>a b c1 c2 c3 d</code><br>
<code>b c1 c2 c3 d</code><br>
<code>c1 c2 c3 d</code><br>
- <code>c2 c3 d</code><br>
</td>
<td>After found matching <code>a b c1 c2 c3 d</code>, the match
process will not discard any result.</td>
</tr>
<tr>
- <td><strong>SKIP_TO_FIRST</strong>[<code>b*</code>]</td>
+ <td><strong>SKIP_TO_FIRST</strong>[<code>c*</code>]</td>
<td>
<code>a b c1 c2 c3 d</code><br>
<code>c1 c2 c3 d</code><br>
@@ -1373,7 +1372,7 @@ Pattern: `a b+` and sequence: `a b1 b2 b3` Then the
results will be:
<td>After found matching <code>a b1</code>, the match process will not
discard any result.</td>
</tr>
<tr>
- <td><strong>SKIP_TO_NEXT</strong>[<code>b*</code>]</td>
+ <td><strong>SKIP_TO_NEXT</strong></td>
<td>
<code>a b1</code><br>
</td>
----------------------------------------------------------------
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]
With regards,
Apache Git Services
