Given that Hadoop is moving over to Avro RPC, and Java, C, and Python
bindings for Avro should be usable by the end of January with the 1.3
release (fingers crossed), would it make sense to spend a bit of energy on
Ruby bindings for Avro as well? If you're interested, I'd be happy to put
you in touch with some folks from Twitter working on the Ruby Avro bindings.
Either way, excited to see the work!
On Tue, Dec 22, 2009 at 10:21 AM, <reynh...@quesera.com> wrote:
> Sounds good. I'll open a Jira ticket when the patches are ready for
> review and discussion. I agree that maintaining the code in multiple
> repositories is something to avoid if at all possible.
> On Mon, Dec 21, 2009 at 04:31:33PM -0800, Mahadev Konar wrote:
> > Hi andrew,
> > If the changes to zookeeper source tree are minor and do not change the
> > functionality of the system/api's/data structures, I think its better to
> > file it as a patch to the main zookeeper source tree. Its would be
> > unadvisable to maintain 2 source tree's for the c code or even a patch in
> > the ruby bindings that applies to the c source tree at runtime
> > I would suggest that you can open a jira and propose the changes that you
> > intend to make on the zookeeper source tree and the reasoning behind it.
> > can discuss any alternatives if we need to on the jira.
> > Thanks
> > mahadev