This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-14
Channels
- # beginners (19)
- # boot (11)
- # cider (59)
- # cljs-dev (292)
- # cljsrn (2)
- # clojure (121)
- # clojure-brasil (19)
- # clojure-canada (2)
- # clojure-france (2)
- # clojure-italy (57)
- # clojure-spec (54)
- # clojure-uk (20)
- # clojurescript (83)
- # core-async (20)
- # cursive (5)
- # datascript (2)
- # datomic (10)
- # duct (25)
- # editors (4)
- # emacs (2)
- # fulcro (5)
- # funcool (1)
- # graphql (2)
- # immutant (8)
- # java (1)
- # jobs (4)
- # jvm (1)
- # keechma (5)
- # luminus (10)
- # off-topic (113)
- # om (36)
- # onyx (11)
- # parinfer (55)
- # pedestal (7)
- # protorepl (28)
- # re-frame (25)
- # reagent (6)
- # ring-swagger (1)
- # shadow-cljs (113)
- # spacemacs (1)
- # specter (23)
- # unrepl (8)
- # yada (8)
not exactly onyx question, but "can I do paginated consumption from kafka topic with gregor?"
you can set ConsumerConfig/MAX_POLL_RECORDS_CONFIG to allow a maximum per poll, but you will get back less, if there are less ready
It’s nice to have, and something which was missing before. I don’t know if a heartbeat is now send when not polling, bu we had problems before when consumers where taking to long, and thought dead, because they took to long after a pol
yeah, writing UI for onyx ETL job reports, and if you are lucky to consume closed topic for huge input file – chrome hangs for minutes
"max.poll.records" is kafka's setting name. gregor
seems to just send it as string w/o any changes. will try it in a few minutes