OSDir

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

triggers in direct runner


Hello Beam Devs,
I'm working on DSL-Euphoria. And I found that when GroupByKey transform is executed on direct runner, window triggers are evaluated element-wise (ReduceFnRunner#processElement) but not actually fired element-wise. They are fired (pane is emitted) when whole batch of elements is processed (ReduceFnRunner#processElements).

I also suspects that elements are already grouped by key when they reach ReduceFnRunner#processElements so triggers are fired only once per whole group.

I'm confused by this behavior since Beam Programming guide has examples with element-wise triggerning (see paragraph 8.4.1.1.).

Is this a wanted behavior? And does every Beam Runner do it the same (portability)? Or do I miss something?

Any kind of help or guidance is appreciated.
Thank you.
Vaclav Plajt


Je dobré vědět, že tento e-mail a přílohy jsou důvěrné. Pokud spolu jednáme o uzavření obchodu, vyhrazujeme si právo naše jednání kdykoli ukončit. Pro fanoušky právní mluvy - vylučujeme tím ustanovení občanského zákoníku o předsmluvní odpovědnosti. Pravidla o tom, kdo u nás a jak vystupuje za společnost a kdo může co a jak podepsat naleznete zde

You should know that this e-mail and its attachments are confidential. If we are negotiating on the conclusion of a transaction, we reserve the right to terminate the negotiations at any time. For fans of legalese—we hereby exclude the provisions of the Civil Code on pre-contractual liability. The rules about who and how may act for the company and what are the signing procedures can be found here.