Github user mushketyk commented on the issue:
https://github.com/apache/flink/pull/2367
@kl0u Sure.
---
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
Github user kl0u commented on the issue:
https://github.com/apache/flink/pull/2367
Hi @mushketyk .
I am trying to clean up a bit the open PRs for the CEP library and the
related JIRAs.
The issue that this PR covers was already implemented as part of multiple
other
Github user LordFB commented on the issue:
https://github.com/apache/flink/pull/2367
Hi @mushketyk,
too bad, with this missing it is kind of a gamebreaker for Flink in my Use
Case.
Jeah, that'd be great, if Till would show some action on this and the
related PRs.
Github user mushketyk commented on the issue:
https://github.com/apache/flink/pull/2367
Hi @LordFB
I don't think there is currently a way to do it in cep-flink. I am still
waiting for Till's review for this PR, but he seems to be really busy with
other work.
Maybe
Github user LordFB commented on the issue:
https://github.com/apache/flink/pull/2367
Hi @mushketyk and @tillrohrmann,
are there any updates on this Pull Request? Or is there already a way to
change the matching behaviour in FlinkCEP?
---
If your project is set up for it,
Github user mushketyk commented on the issue:
https://github.com/apache/flink/pull/2367
Hi @tillrohrmann
I've updated the PR according to your review. I had to add reverse reverse
edges to buffer entries and changed the interface of the SharedBuffer a bit to
move code from it to
Github user mushketyk commented on the issue:
https://github.com/apache/flink/pull/2367
@tillrohrmann Thank you for the very detailed review. I do appreciate it.
I agree with your suggestions and I'll try to improve the code and write
documentation in the next couple of days.
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2367
Thanks for your contribution and apologies for the late review @mushketyk.
I think your implementation goes into the right direction and I really like the
testing.
I think what we
