This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-15
Channels
- # admin-announcements (3)
- # architecture (2)
- # beginners (54)
- # boot (85)
- # braveandtrue (8)
- # cider (21)
- # cljs-dev (56)
- # cljs-site (5)
- # cljsjs (15)
- # cljsrn (9)
- # clojars (4)
- # clojure (99)
- # clojure-austin (1)
- # clojure-russia (36)
- # clojure-spec (53)
- # clojure-uk (29)
- # clojurescript (161)
- # datomic (8)
- # hoplon (3)
- # immutant (48)
- # jobs (1)
- # jobs-rus (1)
- # leiningen (10)
- # om (23)
- # om-next (1)
- # onyx (22)
- # parinfer (3)
- # planck (13)
- # protorepl (8)
- # re-frame (46)
- # reagent (2)
- # remote-jobs (1)
- # respo (1)
- # specter (5)
- # testing (12)
- # untangled (50)
- # yada (13)
@devn: A snapshot build will be cut when master
finishes - https://circleci.com/gh/onyx-platform/onyx-elasticsearch/360
Er, @devth ^ Sorry.
Artifact deployed @ onyx-elasticsearch-0.9.9.1-20160815.153513-2
.
Is there anything special that needs to be done in order to send a sentinel value in for kafka? I set the kafka/partition value and published :done to the topic/partition but the job continued to run
@camechis: Sentinel values aren't supported with multi-partition Kafka topics.
Reliably detecting end-of-stream for that scenario is error-prone, so we punted there.
Ah, should work alright then.
Just :done
. Single keyword
ok, i sent in as a string assuming it would get serialized and deserialized. Using the same Kafka api as the kafka plugin
Strings wont be coerced to keywords
Yup, that should do it.
Probably in the future we'll support an offset as a marker for completion, and avoid using a special value.
That'd be far more robust.