GitHub user dianfu opened a pull request:
https://github.com/apache/flink/pull/4563
[FLINK-7479] [cep] Support to retrieve the past event by an offset
## What is the purpose of the change
*Currently, it's already able to retrieve events matched to the specifed
pattern in IterativeCondition.Context. While there are also requirements to
retrieve events by an physical offset. The retrieved events may not be matched
to any pattern.*
## Brief change log
- *Add API retain() in Pattern*
- *Buffer the past events in NFA.process*
- *Access the past events by the newly added API getEventByOffset in
IterativeCondition.Context*
## Verifying this change
This change added tests and can be verified as follows:
- *Added test in IterativeConditionsITCase*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
## Documentation
- Does this pull request introduce a new feature? (yes)
- If yes, how is the feature documented? (docs / JavaDocs)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dianfu/flink FLINK-7479
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4563.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4563
----
commit e9feb55e6c2f7d32ec6266049be0ea9bbff967b2
Author: Dian Fu <[email protected]>
Date: 2017-08-18T12:50:25Z
[FLINK-7479] [cep] Support to retrieve the past event by an offset
----
---
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.
---
