Github user rtudoran commented on the issue:
https://github.com/apache/flink/pull/3641
@fhueske
Thanks for the feedback - i can of course do the modifications you
mentioned. However, I do not believe that is the correct behavior (or better
said not for all the needed cases). From my understanding of the semantic for
OVER - even if the function would work on the time (proctime/eventtime) - we
should still emit a value for every incoming event. I have 2 arguments for this:
1) in our scenarios - we would use the current implementation for example
to detect certain statistics for every incoming event, while the statistic
focus is defined for a certain period of time (this is a functionality that is
highly needed). For example if you apply this in a stock market scenario - you
might want to say give me the sum of the transactions over the last hour (to
verify potentially a threshold for liquidity of the market) and as the
application would need to react on each incoming transaction (e.g. decide to
buy or not to buy) - then working on the behavior you mentioned would not
enable such a scenario. More than this, even if you would need both behaviors
..then what query could you write to have the described behavior and make the
differentiation from the other?
2) if you think on the case of event time - which should be similar with
proctime - then there it should be the same. When you get an event (ev1 ,
time1) - you should not emit this output until you would know if there is at
some point later another event with the same event time (ev2, time1). Basically
you would register the timer for the acceptable watermark/allowedlatency and
accumulate the accumulator for a specific event time and emit it after the
allowed latency has passed....is this the actual behavior that is implemented /
would be implemented?
---
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.
---
