Regarding the broader sense, I've heard good things about flambo (
https://github.com/yieldbot/flambo), but haven't tried it. Of course, it's
always nice to have something that's written in the language your working
with; as nice as JVM interop is, it can have it's warts. So, the question
stands.
HI MIchael,
Great work. I enjoyed your strangeloop talk.
In the README.md, you stated that Onyx "competes against Storm, Cascading,
Map/Reduce, Dryad, Apache Sqoop, Twitter Crane". Could you please shed
some light on a comparison with Spark? Apparently Spark is on the road to
become a favo
Beautiful :-) Thanks.
Chris
On Sun, Sep 21, 2014 at 9:36 AM, Mike Drogalis wrote:
> Thanks Christopher!
>
> At the moment, elements of a workflow need to strictly be keywords. I'm
> planning to allow for sets of keywords in the roots of the tree to enable
> that expression. For now, you can do
Hi Daniel
This looks like a great project!
Is it possible with onyx to define a workflow with transformers that take
values from multiple sources (inputs or other transformers)?
Chris
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this
Daniel: Haha, yes! Shame that I tried to be smooth in open sourcing it, and
managed to botch it in the worst possible manner.
Rangel: I can't speak to ZeroMQ, but I chose HornetQ because of its
performance, support for transactions, and support for clustering. That
being said, everything that touc
