It should be pretty easy to link together the various recipe's from
the site/wiki and where possible share the recipe documentation across
languages
2008/7/18 Benjamin Reed <[EMAIL PROTECTED]>:
> Some initial implementations of a recipe may only be in C, so it would
> be nice to have a standard wa
Some initial implementations of a recipe may only be in C, so it would
be nice to have a standard way of finding the recipe that wasn't
dependent on the language that implements the recipe.
ben
James Strachan wrote:
> 2008/7/17 Benjamin Reed <[EMAIL PROTECTED]>:
>
>> Excellent proposal. The on
2008/7/17 Benjamin Reed <[EMAIL PROTECTED]>:
> Excellent proposal. The only thing I would add is that there should be
> an english description of the recipe in subversion. That way if someone
> wanted to do a compatible binding they can do it. If the recipe is on
> the wiki it would be hard to keep
As a newbie around hadoop/zookeeper (but long time apache hacker on
various things), I think the high level protocol/recipe stuff should
definitely be a separate, released module; so folks who wanna use it
can share a versioned binary and so forth. It would be awesome to have
a few good protocols/r
Patrick Hunt wrote:
We were thinking of contrib as "interesting stuff that users might want
to re-use/share but not core to zookeeper, we'll carry it around so that
users know where to find it, if it gets broken and no one fixes it it
won't hold up the release"
That's a fine policy for contri
Doug Cutting wrote:
Patrick Hunt wrote:
my original intent was to have it as zookeeper/trunk/src/contrib/...
where this directory will have not only recipes but also other
contributions.
+1 That's what I meant too. And since you've said you want to package
these all as a single jar, then th
Doug Cutting wrote:
Patrick Hunt wrote:
my original intent was to have it as zookeeper/trunk/src/contrib/...
where this directory will have not only recipes but also other
contributions.
+1 That's what I meant too. And since you've said you want to package
these all as a single jar, then th
Patrick Hunt wrote:
my original intent was to have it as zookeeper/trunk/src/contrib/...
where this directory will have not only recipes but also other
contributions.
+1 That's what I meant too. And since you've said you want to package
these all as a single jar, then there should just be a
Doug Cutting wrote:
Patrick Hunt wrote:
1) I think we should have a
"contrib/recipes/{java/{main,test}/org/apache/zookeeper/... ,c/,...}"
hierarchy for contributions that implement recipes, including any
helper code
Are folks expected to be able to use this code as-is? Are these, in
effect
I was thinking all the recipe implementations are in a single jar.
zookeeper-recipes.jar
otw it's going to be a pain to carry around the "right" jars - esp if
one recipe depends on another. We saw similar issue with Pig UDF
contribs (originally there were multiple jars).
Patrick
Doug Cuttin
Patrick Hunt wrote:
should we have separate contrib subdirs, one for each recipe or all
recipes together? What about shared code, common code for implementing a
recipe? Seems a little too much to separate them all at the top level,
rather than separating them in packages
Do you want to packag
ries to explain what its doing?
mahadev
-Original Message-
From: Benjamin Reed [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2008 10:33 AM
To: zookeeper-dev@hadoop.apache.org
Subject: Re: Recipe contrib -- was Re: [PATCH] a simple Leader
Election or
exclusive Write Lock
Patrick Hunt wrote:
1) I think we should have a
"contrib/recipes/{java/{main,test}/org/apache/zookeeper/... ,c/,...}"
hierarchy for contributions that implement recipes, including any helper
code
Are folks expected to be able to use this code as-is? Are these, in
effect, libraries? If so,
I've created a Jira for us to discuss/document this:
https://issues.apache.org/jira/browse/ZOOKEEPER-80
I will make 78/79 depend on this
78 is James' patch - may require some rework after 79/80 are finalized
79 is documentation of the leader election protocol that jacob outlined
Patrick
Benja
, July 17, 2008 10:33 AM
> To: zookeeper-dev@hadoop.apache.org
> Subject: Re: Recipe contrib -- was Re: [PATCH] a simple Leader
Election or
> exclusive Write Lock protocol/policy
>
> Excellent proposal. The only thing I would add is that there should be
> an english description of the
Excellent proposal. The only thing I would add is that there should be
an english description of the recipe in subversion. That way if someone
wanted to do a compatible binding they can do it. If the recipe is on
the wiki it would be hard to keep it in sync, so it is important that it
is in subvers
James, thanks for the contribution! Tests and everything. :-)
Jacob sent some mail to the list recently (attached) that details a
protocol that he's used successfully (and picked up by some zk users). I
have a todo item to document this protocol on the recipes wiki page,
haven't gotten to it y
17 matches
Mail list logo
