Yes - I am able to process matched out patterns. Let's suppose I have an order fulfillment process.
I want to know how many fulfillments have not met SLA and further how late they are and track until they are fulfilled. >From what I tried with samples, once the pattern timeout, it is discarded and events that come after that are ignored (not applied to the pattern). Is there a better way to do it using Table API? Where I am able to emit an event (alert) when the timeout happens, and it continues to alert me - hey you fulfillment is delayed by 6 hours, 12 hours and so on and also know when it is finally completed. On Thu, Jul 16, 2020 at 3:08 PM Chesnay Schepler <ches...@apache.org> wrote: > Have you read this part of the documentation > <https://ci.apache.org/projects/flink/flink-docs-release-1.11/dev/libs/cep.html#handling-timed-out-partial-patterns> > ? > > From what I understand, it provides you hooks for processing matched/timed > out patterns. > > On 16/07/2020 20:23, Basanth Gowda wrote: > > Hello, > > We have a use case where we want to know when a certain pattern doesn't > complete within a given time frame. > > For Example A -> B -> C -> D (needs to complete in 10 minutes) > > Now with Flink if event D doesn't happen in 10 minutes, the pattern is > discarded and we can get notified. We also want to track how many of them > completed (even if they meet SLA). How do we achieve this with FLINK CEP or > other mechanisms? > > thank you, > Basanth > > >
