This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-26
Channels
- # adventofcode (2)
- # beginners (69)
- # boot (37)
- # cider (6)
- # clara (31)
- # cljs-dev (75)
- # cljsrn (5)
- # clojure (72)
- # clojure-dev (7)
- # clojure-italy (11)
- # clojure-nl (8)
- # clojure-russia (2)
- # clojure-spec (56)
- # clojure-uk (54)
- # clojure-za (1)
- # clojurescript (156)
- # cursive (2)
- # datomic (34)
- # emacs (1)
- # fulcro (227)
- # hoplon (74)
- # jobs (1)
- # jobs-discuss (16)
- # leiningen (5)
- # lumo (17)
- # off-topic (9)
- # om (3)
- # onyx (10)
- # other-languages (1)
- # portkey (2)
- # re-frame (2)
- # reagent (36)
- # reitit (1)
- # remote-jobs (1)
- # ring-swagger (8)
- # shadow-cljs (85)
- # slack-help (2)
- # spacemacs (6)
- # specter (3)
- # sql (17)
- # test-check (15)
- # tools-deps (80)
I'm currently playing around with Onyx in the context of a small hobby project and I ran into an issue the other day, which I posted to SO: https://stackoverflow.com/questions/51038280/onyx-cant-pick-up-trigger-emit-results-in-the-next-task
Basically, I wanted to understand aggregate some data and hand it to the next task and thought :trigger/emit
would be the way to go and then the next task never saw the emitted segments.
Now, I finally saw that there was a warning / error in the log file that pointed to a missing peer configuration of :onyx.peer/storage.zk.insanely-allow-windowing?
While this now makes my toy example working, this option (and the corresponding commit in Onyx) doesn't look like this is a good idea.
If the only reason it didn’t work was :onyx.peer/storage.zk.insanely-allow-windowing?
, then that means everything else around :trigger/emit
was ok.
I would just recommend switching to S3 checkpointing, as you will have trouble with ZK based window checkpoints.