You might want to add a link to zkclient on this page:
http://wiki.apache.org/hadoop/ZooKeeper/UsefulTools
Patrick
Patrick Hunt wrote:
Ted Dunning wrote:
Judging by history and that fact that only 40/127 issues are resolved,
3.3
is probably 3-6 months away. Is that a fair assessment?
Hi Patrick,
thanks - we will do, also thanks for all the feedback.
Stefan
On Oct 5, 2009, at 11:22 AM, Patrick Hunt wrote:
You might want to add a link to zkclient on this page:
http://wiki.apache.org/hadoop/ZooKeeper/UsefulTools
Patrick
Patrick Hunt wrote:
Ted Dunning wrote:
Judging by
I started looking a bit more closely at the source, some questions:
1) I tried generating the javadocs (see my fork of the project on github
if you want my changes to build.xml for this) but it looks like there's
pretty much no javadoc. Some information, particularly on semantics of
Hi Patrick,
On 01.10.2009, at 08:57, Patrick Hunt wrote:
I started looking a bit more closely at the source, some questions:
1) I tried generating the javadocs (see my fork of the project on
github if you want my changes to build.xml for this) but it looks
like there's pretty much no
I think that another way to say this is that zkClient is going a bit for the
Spring philosophy that if the caller can't (or won't) be handling the
situation, then they shouldn't be forced to declare it. The Spring
jdbcTemplate is a grand example of the benefits of this.
First implementations of
There is not much way to totally avoid this without massive performance loss
because the connection loss could be during the the time that the
confirmation is returning.
You may be able to tell if the file is yours be examining the content and
ownership, but this is pretty implementation
I'm on the fence about checked vs. unchecked, but I think Javadoc that
declares what exceptions are thrown would help users figure out if
they might want to catch something.
Additionally some of the ZkClient method semantics are confusing. For
example, create() returns the path of the created
Peter Voss wrote:
On 01.10.2009, at 08:57, Patrick Hunt wrote:
2) what purpose does ZkEventThread serve?
ZkClient updates it's connection state from the ZooKeeper events. Based
on these it notifies listeners, updates it's connection state or
reconnects to ZooKeeper. ZkClient has its own
Not to harp on this ;-) but this sounds like something that would be a
very helpful addition to the README.
Ted Dunning wrote:
I think that another way to say this is that zkClient is going a bit for the
Spring philosophy that if the caller can't (or won't) be handling the
situation, then they
That looks really lovely.
Judging by history and that fact that only 40/127 issues are resolved, 3.3
is probably 3-6 months away. Is that a fair assessment?
On Thu, Oct 1, 2009 at 11:13 AM, Patrick Hunt ph...@apache.org wrote:
One nice thing about ephemeral is that the Stat contains the owner
Ted Dunning wrote:
Judging by history and that fact that only 40/127 issues are resolved, 3.3
is probably 3-6 months away. Is that a fair assessment?
Yes, that's fair.
Patrick
On Thu, Oct 1, 2009 at 11:13 AM, Patrick Hunt ph...@apache.org wrote:
One nice thing about ephemeral is that the
11 matches
Mail list logo
