This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-26
Channels
- # arachne (4)
- # beginners (70)
- # bigdata (1)
- # boot (373)
- # braid-chat (3)
- # cider (4)
- # cljs-dev (10)
- # cljsjs (6)
- # cljsrn (27)
- # clojars (11)
- # clojure (114)
- # clojure-austria (1)
- # clojure-czech (2)
- # clojure-dusseldorf (2)
- # clojure-greece (7)
- # clojure-italy (2)
- # clojure-nl (6)
- # clojure-russia (15)
- # clojure-serbia (11)
- # clojure-spec (92)
- # clojure-uk (5)
- # clojurescript (183)
- # component (9)
- # cursive (28)
- # datomic (36)
- # editors (4)
- # emacs (1)
- # garden (11)
- # hoplon (155)
- # lein-figwheel (7)
- # mount (47)
- # om (97)
- # onyx (25)
- # proton (3)
- # rdf (3)
- # re-frame (80)
- # reagent (9)
- # ring-swagger (9)
- # spacemacs (1)
- # untangled (145)
- # vim (2)
Any reason that sql/upper-bound and sql/lower-bound are not document in onyx-sql information model ?
Hmm. No good reason
Also needs to be described in the README and the task schema
I need to expose the partition-table’s min/max for usage in the one or more lifecycles, will you accept a pull request for this ?
Could you expose it through the task map instead?
Assuming it passed schema checks, etc
I don’t see who I could do that, since the min and max is calculated in in partition-table-by-uuid and partition-table, Unless I always configures lower/upper-bound from outside. As it is now there is now way to exactly to reproduce the result from partition-keys if (the database changes between submits)
Unless what you mean is that you want that information in the task map?
I mean in the event map
correct in the event-map 🙂
Is there a kinesis plugin in the pipes (should I copy from kafka?)
@zamaterian sure, I’d take PR for that. If you could document the lower and upper-bounds that would be even better
@timothypratley not currently in the works, however I’d love for one to exist
No problem, will do both 🙂
Copying from Kafka would probably be the best bet.
Thanks!
Th documentation is that done solely in the information model ?
Currently it’s in 3 places, but we will eventually generate them all from the information model.
README, onyx.tasks.sql for the task bundle (schema needs those keys added), and the information model
I'm going to binge-fix all the plugins one day so their README's are generated from the info model.
Probably on a day when Im flying or something.
Gotta be done. Getting the info models done was a good first step
The formatting is the hard part
If anyone wants to contribute, that'd be a great place to help. Granted it's not particularly exciting work, but an important contribution none-the-less.