morning all, I'm getting the above errors - the first is output to stdout and the second is what is put in onyx.log

I've no idea what is going on so if anyone has any insights I'm happy to hear them

https://www.youtube.com/watch?v=iH5Mon8IG0g

Is there a way to tag data in a session window when it fires a trigger? So far all I've got is the ability to touch a profile in DB or something like that. I would like to tag the data, however, so that other stages may reason about the tagged data. Another possible solution is emitting data/segments from triggers to stages, but I'm less confident in this possibility.

@theblackbox Custom refinement

interesting......

cheers @michaeldrogalis I think I've managed to refactor my logic into two distinct types of predicate: onest that injest single events and ones that injest state and I think this clears things up for me, but I will keep that in mind in case I need to reconsider

@michaeldrogalis great talk, I'm looking forward to seeing Pyroclast finished!

are you planning on describing some of the technical details on your site ? I understand all the goals that Pyroclast wants to achieve, but I'm not exactly sure how it does it

this matters a great deal to me though

especially since it talkes so difficult a set of problems to do correctly

*tackles

@lmergen If you haven’t already, I suggest taking a look at onyx-local-rt to get some insight into the technical side of how we’re handling some of these problems. https://github.com/onyx-platform/onyx-local-rt

It’s Onyx for cljc, reusing a lot of the core while eliding things incompatible with the browser.

Thinking of using it to quickly prove out pipelines before moving them to distributed mode

@lmergen We’ll get around to getting up some text soon about the idea of how it works. Lot going on right now, but it’ll be a priority in April.

cool! no need to rush, just chiming in with my thoughts