This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-01
Channels
- # beginners (117)
- # boot (8)
- # cider (22)
- # clara (3)
- # clojure (79)
- # clojure-italy (3)
- # clojure-spec (34)
- # clojure-uk (34)
- # clojurescript (74)
- # cursive (7)
- # datascript (5)
- # datomic (28)
- # defnpodcast (1)
- # dirac (9)
- # docker (25)
- # duct (1)
- # emacs (14)
- # fulcro (67)
- # graphql (1)
- # hoplon (15)
- # jobs (4)
- # juxt (6)
- # off-topic (76)
- # parinfer (3)
- # re-frame (25)
- # reagent (4)
- # rum (6)
- # shadow-cljs (1)
- # spacemacs (30)
- # sql (15)
- # unrepl (36)
- # yada (1)
morning!
Morning all
@carr0t Oversleeping? Sounds glorious
Only managed to make it work because my wife is into her office a bit later today, so I could ask her to walk the dog
Do you have any children other than the dog?
This is neat too https://clojure.org/guides/spec#_testing
have a child, can confirm, dogs are ace. They don't take 18 years to become self sufficient.
So babies could arguably do those things naturally given time, just not to the way we want them to
any cassandra users out there interested in a small-to-medium scale non-blocking roughly-constant-memory client-side join implementation ?
@mccraigmccraig Yes, not that I can claim to be a Cassandra user (at the moment) but I am interested in seeing that anyway 🙂
here you go @maleghast https://github.com/employeerepublic/promisespromises/blob/master/src/prpr/stream/cross.clj#L384 - it combines manifold streams containing values sorted by a key and is capable of doing things like sort-merge, join and various similar set operations
since cassandra doesn't have any join implementation, but can sort records for you (particularly easy with MVs) this makes it straightforward to do a client-side join, as long as your cassandra client can give you a manifold stream of records for a query https://github.com/employeerepublic/er-cassandra/blob/master/src/er_cassandra/model/select.clj#L16
it's not really constant-memory because it buffers all records for each join key, so some very-many<->very-many joins could blow memory, but as long as you don't have any data like that it's good