This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-20
Channels
- # ai (1)
- # beginners (17)
- # boot (27)
- # cider (2)
- # cljs-dev (64)
- # clojure (131)
- # clojure-austin (13)
- # clojure-dev (15)
- # clojure-dusseldorf (11)
- # clojure-france (45)
- # clojure-russia (19)
- # clojure-spec (66)
- # clojure-uk (22)
- # clojurescript (97)
- # core-logic (7)
- # cursive (5)
- # data-science (1)
- # datomic (92)
- # dirac (49)
- # emacs (1)
- # events (5)
- # funcool (10)
- # hoplon (79)
- # jobs (1)
- # jobs-rus (1)
- # lein-figwheel (1)
- # leiningen (3)
- # om (14)
- # onyx (35)
- # planck (2)
- # proton (1)
- # re-frame (21)
- # reagent (2)
- # ring-swagger (10)
- # spacemacs (10)
- # specter (18)
- # untangled (7)
- # vim (23)
Anyone want to have a go at this? š
https://www.reddit.com/r/Clojure/comments/58avz6/onyxlocalrt_a_new_clojurescript_compatible/d8zjcg1
This would need very little involvement from any of @lucasbradstreet, @gardnervickers, or myself, so ideal for a side project to incrementally hack on, maybe as a group.
@michaeldrogalis I don't see a task there, just the link to local-rt
Is there a way to check after running a while whether Onyx had to handle any duplicates, network errors, crashing etc?
especially the application level stuff, if RocksDB has any use, if something had to be replayed
Metrics definitely helps, though there may be some places that we need some additional metrics in places
Retries are definitely an important one
@michaeldrogalis, I'll have a go at making an interactive tutorial.
@colinhicks Ah, brilliant. š Btw, the doc tool hasn't slipped off my radar. Still searching for some time to integrate it, but Im eager.
No prob. I could spend some time on docs, too, soon -- it's nice to be back from hurricane internet/power outages.
Oh, yikes. You were in the middle of all that?
yeah. not our first rodeo, though, so we were prepared & safe. Just a bit unlucky this time with a group of trees creaming a utility pole down the street
Glad you're alright. That's frustrating, though. š
Yep. Although good to get off the grid every now and then, even unwittingly. Onyx stickers rode the whole thing out in the mailbox. ... Something something great fault tolerance.
Haha š
Ha! š
* Exactly one sticker not guaranteed
I sent a bunch, mostly because I always get an air bubble the first time
So for the interactive examples/tutorial, one interesting direction might be to go through the docs and lift the examples right out. We could look at bringing the interactive examples inline with the docs in the future. http://www.onyxplatform.org/docs/user-guide/0.9.11/#flow-conditions
But Im pretty much open to whatever anyone finds useful. This should be a really cool area to explore
Yeah, that sounds great. Awesome literate programming opportunity. I'll put up an issue later today or tomorrow so we can all brainstorm.
That's fantastic. Thanks so much for taking the lead š This'll go a long way to showing how Clojure really shines for this stuff.
Concerning, aggregations What would be an example where the logic of the aggregation-fn
would be different then that of the super-aggregation
function. Im trying to write another chapter in learn-onxy on aggregations.
https://github.com/onyx-platform/onyx/blob/75a48ce99f7d9cc829ea27922d987617abc7c5ac/src/onyx/windowing/aggregation.cljc
I suppose iām not sure why both of them are necessary.
@drewverlee super-aggregation's are necessary when two windows need to merge together.
The only mergable window's that Onyx offers are Session windows.
If you had two windows that were aggregated by count, and some data bridged those two windows into one session, you need to sum the counts to combine the windows into one.
Very easy to simulate the moment just before and after window merging using local-rt.