You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm really interested in this. But perhaps an explanation here would help too: when it says they're emitted downstream, how does one control that, e.g. via flow conditions? Are they emitted as segments of the task the trigger is related to? Something else?
Yes, they are subject to flow conditions. Hopefully I’ll get around to the example soon (though we’d love to merge a PR from you).
If you wish to excuse the regular segments, you can use the new onyx/type :reduce.
On 11 Jan 2018, at 18:35, Roman Pearah ***@***.***> wrote:
I'm really interested in this. But perhaps an explanation here would help too: when it says they're emitted downstream, how does one control that, e.g. via flow conditions? Are they emitted as segments of the task the trigger is related to? Something else?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
It would be great to have an example of a trigger that emits segments when fired. Think the aggregation example could be extended to have that.
The text was updated successfully, but these errors were encountered: