See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/25/changes
Changes:
[phunt] Moved the cobertura taskdef into the cobertura target - the regular
targets always work now and the cobertura targets will work if the coberbura
jars are available
added a high level protocol/feature - for easy Leader Election or exclusive
Write Lock creation
---
Key: ZOOKEEPER-78
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-
[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-78:
Attachment: writeLock_protocol.patch
> added a high level protocol/feature - for easy Lea
So having recently discovered ZooKeeper, I'm really liking it - good job folks!
I've seen discussions of building high level features from the core ZK
library and had not seen any available on the interweb so figured I'd
have a try creating a simple one. Feel free to ignore it if a ZK ninja
can th
Document jacob's leader election on the wiki recipes page
-
Key: ZOOKEEPER-79
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-79
Project: Zookeeper
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614431#action_12614431
]
james strachan commented on ZOOKEEPER-79:
-
BTW https://issues.apache.org/jira/bro
[
https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614435#action_12614435
]
Patrick Hunt commented on ZOOKEEPER-79:
---
I know, your submission (78) is what kicke
[
https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614448#action_12614448
]
james strachan commented on ZOOKEEPER-79:
-
Ah cool :) Was just checking we were n
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
[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar reassigned ZOOKEEPER-78:
--
Assignee: james strachan
assiging this to james since he is working on this.
> added
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
Document process for client recipe contributions
Key: ZOOKEEPER-80
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-80
Project: Zookeeper
Issue Type: Task
Components: documentati
I agree with Ben. Can we have something like?
Contrib/recipes/leaderelection
Or
Contrib/recipes/locking/
And a README inside each of these directories to explain what its doing?
mahadev
> -Original Message-
> From: Benjamin Reed [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 17, 200
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
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,
[
https://issues.apache.org/jira/browse/ZOOKEEPER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614466#action_12614466
]
Doug Cutting commented on ZOOKEEPER-80:
---
Whoa! Big issue description! Perhaps you
I didn't get that from Ben's comment, I thought he was talking about
including the docs into contrib/recipes rather than in
trunk/src/docs/... (which makes sense to me, also makes sense in light
of doug's subsequent comments on this thread).
should we have separate contrib subdirs, one for eac
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
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
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
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:
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:
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
[
https://issues.apache.org/jira/browse/ZOOKEEPER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-80:
--
Description:
Per Doug's suggestion I'll use a link instead of copy/paste:
http://mail-archiv
[
https://issues.apache.org/jira/browse/ZOOKEEPER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614540#action_12614540
]
Benjamin Reed commented on ZOOKEEPER-38:
I really like how you pulled the code ou
[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614548#action_12614548
]
Flavio Paiva Junqueira commented on ZOOKEEPER-78:
-
This is a nice impleme
[
https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614556#action_12614556
]
Flavio Paiva Junqueira commented on ZOOKEEPER-79:
-
This idea of having cl
[
https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614558#action_12614558
]
Flavio Paiva Junqueira commented on ZOOKEEPER-79:
-
And, I like Jacob's su
29 matches
Mail list logo
