Recently I was studying Stuart Sierra's clojure-hadoop project¹, and
there saw a technique that I'd like to discuss. There's a Java class
generated whose method definitions get patched based on a provided
configuration, and I'd like to understand the scope of this patching and
why the technique's
Hi Steven
just fyi - more recent version of clojure-hadoop is available at
https://github.com/alexott/clojure-hadoop - it includes many
patches/improvements
On Tue, Mar 6, 2012 at 5:18 PM, Steven E. Harris s...@panix.com wrote:
Recently I was studying Stuart Sierra's clojure-hadoop project¹,
On Tuesday, March 6, 2012 11:18:50 AM UTC-5, Steven E. Harris wrote:
If this impact is global, is it the case that this software never needs
to accommodate instances of these generated classes with different
configurations?
I haven't looked at that code in a long time, but the answer is
Stuart Sierra the.stuart.sie...@gmail.com writes:
I haven't looked at that code in a long time, but the answer is yes. Each
Hadoop Job runs in its own JVM process.
Thank you. That makes sense, then.
Just to nail it home, though, do you agree that this patching technique
is generally /not/
