Github user kl0u commented on the issue:
https://github.com/apache/flink/pull/2361
Well for iii), the idea behind the new type of state is that the `NFA` will
see one `PotentiallyFinal` element, but it will continue receiving, until the
first non-eligible element. So if the pattern says sth like `'a'.oneOrMany`,
the `a` will be `PotentiallyFinal` with a self-loop. So the `NFA` will have to
set a flag, e.g. `canTerminate` to `true`. Then another `a`, still valid, so
the `NFA` will accept it, and then a `b`. In this case, the `NFA` should
declare the previous as a matching pattern, emit it, and then continue with the
`b`. The current `NFA` would not recognize the `PotentiallyFinal` state.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
