hadoopy backend? about dumbo HOT 4 OPEN

I would help with this if there is interest. The purpose of Hadoopy isn't to recreate this functionality, it is to create a thin core python interface for streaming. I use whirr and oozie for cluster and job management respectively (Hadoopy is designed to be compatible with these tools). I can see more casual users not wanting to use these more powerful but complex tools, opting for a more integrated approach.

There are a few things we need to take into account.

1. Practically, I'd need to relicense my code so that it is compatible (David and Andrew are the only other contributors). This shouldn't be a problem and I'd be willing to do that (I'd most likely dual license it).
2. Should it be part of dumbo, optional, or a separate fork? I think the cleanest solution is that dumbo can optionally use Hadoopy as a backend if it is available.
3. Backwards compatibility is going to be an important focus. I'd want to find a diverse set of Dumbo users to work with us running legacy code. Unit tests can help here.

from dumbo.

I'd definitely be interested and I'd be happy to review code or help out with figuring out how to hook things up or so. As I'm pretty busy these days I probably won't be able to help with the actual coding though, but it looks like we might already have enough manpower to get something done I guess. So bring on the code -- I look forward to having a look at it and trying it out.. :)

from dumbo.

Okay, this sounds like something worth pursuing. (At least, I would really like it. I had to switch back to dumbo for some last minute tests in a paper recently because I needed some of the libegg/libjar/etc. features.)

One question: Would you need to dual license it if dumbo just used it as a black-box backend? (I am not up to speed on how python's "import" acts with respect to licenses.) I agree that this is the cleanest approach.

from dumbo.

Not sure about the licensing either, but surely we could figure something out...

from dumbo.