Fork me on GitHub
#onyx
<
2017-08-30
>
emergence21:08:31

:error {:task-map {(not (= (name (:onyx or :kafka)) (namespace a-clojure.lang.Keyword))) invalid-key}}}

emergence21:08:50

Tried posting more but Slack says no storage left

michaeldrogalis21:08:28

@emergence It’s complaining about the namespace of a key in your catalog.

michaeldrogalis21:08:40

Are you using an undefined :onyx/* or :kafka/* keyword?

michaeldrogalis21:08:45

We restrict those keys to detect typos.

michaeldrogalis21:08:17

Schema’s output is pretty trash 😕

devth21:08:57

any plans to migrate to clojure.spec? didn't find anything after a quick google search.

emergence21:08:30

I was working with an example using an older version of onyx-kafka so it's possible -- this is my config.edn

{:env-config
 {:onyx/tenancy-id #profile {:default "1"
                             :docker #env ONYX_ID}
  :zookeeper/address #profile {:default "127.0.0.1:2181"
                               :docker "zookeeper:2181"}
  :onyx.log/config #profile {:default nil
                             :docker {:level :info}}}
 :peer-config
 {:onyx/tenancy-id #profile {:default "1"
                             :docker #env ONYX_ID}
  :zookeeper/address #profile {:default "127.0.0.1:2181"
                               :docker "zookeeper:2181"}
  :onyx.peer/job-scheduler :onyx.job-scheduler/balanced
  :onyx.messaging/allow-short-circuit? #profile {:default false
                                                 :docker true}
  :onyx.messaging/impl :aeron
  :onyx.messaging/bind-addr #or [#env BIND_ADDR "localhost"]
  :onyx.messaging/peer-port 40200
  :onyx.messaging.aeron/embedded-driver? #profile {:default true
                                                   :docker false}
  :onyx.log/config #profile {:default nil
                             :docker {:level :info}}}
 :kafka-config
 {:onyx/name :in
  :onyx/plugin :onyx.plugin.kafka/read-messages
  :onyx/type :input
  :onyx/medium :kafka
  :kafka/topic "answers"
  :kafka/group-id "onyx-consumer"
  :kafka/receive-buffer-bytes 307200
  :kafka/zookeeper "127.0.0.1:2181"
  :kafka/offset-reset :earliest
  :kafka/commit-interval 500
  :kafka/deserializer-fn :streaming-answers.util/deserialize-message-transit
  :kafka/wrap-with-metadata? false
  :onyx/min-peers 1
  :onyx/max-peers 1
  :onyx/batch-size 100
  :onyx/doc "Reads messages from a Kafka topic"}
 :batch-config
 {:onyx/batch-size 1
  :onyx/batch-timeout 1000
  :onyx/min-peers 1
  :onyx/max-peers 1}}

emergence21:08:47

Yes I used to like schema but since spec came along ... 🙂

michaeldrogalis21:08:22

What versions are you on?

emergence21:08:47

[org.onyxplatform/onyx "0.10.0"]
                 [org.onyxplatform/onyx-kafka "0.10.0.0"]
                 [org.onyxplatform/lib-onyx "0.10.0.0"]

michaeldrogalis21:08:28

I bet it’s commit-interval

michaeldrogalis21:08:36

We might have forgotten to remove that from the examples

emergence21:08:44

I hava Kafka, zookeeper and dash running ... can also start peer though I get this error re: logging

Incompatible versions of the Onyx cluster coordination log.
                     A new, distinct, :onyx/tenancy-id should be supplied when upgrading or downgrading Onyx. {:cluster-version "0.9.16-SNAPSHOT", :peer-version "0.10.0"}

emergence21:08:18

going to try to remove that key and see what happens (commit-interval)

michaeldrogalis21:08:27

Yeah you’re going to need to wipe ZK or use a new tenancy ID. 0.9 and 0.10 are incompatible

emergence21:08:52

ok will tweak that too

emergence21:08:19

Thanks for your help on this btw 🙂

emergence21:08:25

@michaeldrogalis bumping tenancy-id cleared the incompatibility error and pulling that key allowed me to submit my job -- thanks!