@michaeldrogalis Is your answer here still correct? https://groups.google.com/d/msg/onyx-user/FWUS7r6C4ww/7bA7cXnVAwAJ I was using emit yesterday, but if the original task function returns nothing, then the window never gets populated, and so the trigger emit has no data to send downstream. But if I use ‘identity’ (like in the twitter example), then I have both the original segment and the emitted segment passed downstream. My workaround was to have emit wrap the segment and then use a flow condition to prevent the original task fn from sending segments. But… seems like I’m doing something wrong.

@wildermuthn We’re actually about to fix this - that is the workaround currently.

I just didn’t make the right call when we originally implemented this.

Expecting to have a patch out for this in the next week or 2.

ok awesome!

I feel less stupid now. 🙂

Haha good, not your fault.

@wildermuthn Proposed solution is by default disallow segments flowing to downstream tasks when trigger/emit is on and extend flow conditions to to handle trigger/emit segments first class.

i assume org.onyxplatform/onyx-peer-http-query "0.10.0.0" won't work with onyx 0.9.x, correct? curious because i'm wanting to get the prometheus /metrics endpoint but haven't upgraded to 0.10 yet

@devth Much to Rich’s dismay, 0.9 and 0.10 are incompatible, yes

haha. ok thanks. hopefully we'll make the upgrade to 0.10 soon. can't wait to see prom metrics 😄

This should help though - https://github.com/onyx-platform/onyx-peer-http-query/tree/0.9.x

yep i am running that currently. but as far as i could tell, /metrics was added in 0.10

Ah, I recalled wrong. Thought we had that for 0.9 too. Yeah, gotta be on 0.10 then

@michaeldrogalis That solution sounds great. I have an additional flow condition downstream from the emitter that would fit more correctly for the emitter itself.

@wildermuthn Cool, we’ll run the specifics we’re thinking by you to make sure it’ll work for your use case before we get going.

Thanks!