Fork me on GitHub

@yonatanel Thanks, fixed in b3e1882b444be75b97bfc322e31393115ea9a941 on develop.


And, what @camechis said is correct.


How do I invalidate Onyx's state (checkpoints, aggregation state in BookKeeper etc.) if I want a clean reprocessing of all my data?


These are scoped to job id, so you should get a clean reprocessing without doing anything.


I see that resubmitting the same job-id is not possible. Does that mean Onyx will resume on its own when started after a total crash or shutdown?


The only exception is if a job was killed for some reason (exception was thrown that was unhandled by lifecycle/handle-exception or flow conditions)


What if I don't want it to resume? If I killed it on purpose so it would stop a faulty processing with nasty side effects.


There's kill-job, but that won't be invoked if I hysterically pull the plug of the machine :)


You can pull the plug, then bring the machine back up, don’t start the peers, call onyx.api/kill-job which will write a message to zookeeper (note that the peers aren’t up), then start the peers up


Hello everyone. In preparation for something we'll be putting out in the next 24 hours, we put up a mostly complete/mostly accurate Spec for Onyx. Should be useful.


We stopped short of finishing the Spec in its entirety for all of the internal Onyx components because most people will not need them. This should be treated as experimental, and is not used for validation yet. We need to backport our pretty-errors that work against Schema to use Spec instead.


If you spot any errors, please open an issue. Much of this file was automatically generated, and the tool that does the generation still needs to be extracted from another project.


I'm searching onyx source code to see how passing vector input to core-async plugin works. I've noticed test in learn-onyx knows when the task is done and triggers a window trigger even though there are less segments in the input than the tigger threshold. Any pointers?


Never mind. It's the bind-inputs! function in each challenge in learn-onyx. 😬


I already have in my todo list to implement a vec/seq plugin, manifold plugin and kinesis plugin. How much of a waste is it?


Manifold is also compatible with core.async channels from what I remember, a Kinesis plugin would be fantastic though!