This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 205
:trigger/emit not working with :onyx.triggers/watermark #839
Comments
Is this the same problem as #840? |
I don't believe so as there's no Kafka involved. Here I was trying to implement the new emit capability but couldn't get it to work with a watermark trigger. It's possible that it's just something else I don't understand about watermarks. The trigger fires if I use sync, but nothing goes to the output-ch if I use emit instead. |
Okay, thanks. I’ll look into this one when I get a moment.
… On 21 Jan 2018, at 15:25, Roman Pearah ***@***.***> wrote:
I don't believe so as there's no Kafka involved. Here I was trying to implement the new emit capability but couldn't get it to work with a watermark trigger. It's possible that it's just something else I don't understand about watermarks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I am meeting the same issue and :trigger/emit used to be working with :onyx.triggers/watermark in 0.12.2, but seems it's broken in recent releases. |
looks like I have to set batch-size=1 to get all outputs when playing with trigger. If I set batch size > size of input data, I get nothing. If I set batch size > 1 and < size of input data, I missed some data in the end. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using a watermark trigger, emitted segments don't flow downstream (as they do with a segment-based trigger, for instance). Perhaps it's unsupported for that trigger type, though I cannot imagine why that would be the case since I confirmed that the emit function is firing as expected. Here's a runnable example:
The text was updated successfully, but these errors were encountered: