Clojurians Log v2
Clojure programming
Channels
Apps
onyx
FYI: alternative Onyx :onyx: chat is at <https://gitter.im/onyx-platform/onyx> ; log can be found at <https://clojurians-log.clojureverse.org/onyx/index.html>
xiongtx 2018-09-25T22:37:51.000100Z
When creating a sliding window based on elements rather than time, what should be the value of :window/window-key? Doesn't seem like it should be necessary, but the docs say it's required: http://www.onyxplatform.org/docs/cheat-sheet/latest/#window-entry/:window/window-key
Lutz 2018-09-26T08:32:44.000100Z
Having considered this, too, I think the problem with window based on a fixed number of elements cannot be done in general. If your task is setup to run on more than one peer, there is no way for these peers to tell how many segments there have been in the current window.
Lutz 2018-09-26T08:37:01.000100Z
If you mean sliding window based on some key with real number values rather than timestamps, I cannot see a reason why this should not work. As far as I can tell, this is not supported by onyx. If you really need to make it work, you can consider the hack of mapping your real values to timestamps, while preserving the ordering and translating the respective ranges. Needless to say, this would be bad practice.
xiongtx 2018-09-25T22:43:59.000100Z
Also, can the window's trigger pass the window of elements to a downstream task? All the learn-onyx examples just have the state put into an atom.
I'm basically trying to replicate a pattern in core.async whereby a partition transducer is used to create windows of elements in a channel, which can then be processed downstream.