Currently event time can be handled on the operator level with time bucketing (which allows for late / out of order arrival). We are planning to generalize this in the future.
Thomas On Fri, Mar 18, 2016 at 12:00 PM, Christian Hellström <psilonl...@gmail.com> wrote: > Ok, thanks. Are there plans to support event-time processing? > > That would work with the separate path in the DAG. Cool! > On 18 Mar 2016 19:58, "Sandesh Hegde" <sand...@datatorrent.com> wrote: > >> Hello Christian, >> >> Apex doesn't have a support for event time processing. For the second >> scenario, how about creating a separate path in the DAG based on the >> content? >> >> Thanks >> Sandesh >> >> On Fri, Mar 18, 2016 at 11:49 AM Christian Hellström < >> psilonl...@gmail.com> wrote: >> >>> The doc states that the order of events in processors is preserved >>> (based on how they are emitted), but does that mean that there is no >>> event-time concept that allows out-of-order processing of events? >>> >>> Moreover, can events be re-prioritized based on their contents, e.g. >>> when they contain special phrases (e.g. AUTH in a security context). NiFi >>> allows this, which is useful in situations with limited bandwidth. I was >>> just wondering... >>> >>> Thanks! >>> >>
