giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianmarco De Francisci Morales <g...@apache.org>
Subject Re: [jira] [Commented] (GIRAPH-540) Improved ZooKeeper Library
Date Mon, 04 Mar 2013 22:53:35 GMT
Actually, unless you use some specific recipe from Curator (like the
cache), your are just adding complexity.
You need one more dependency, one more thing that can break, one more thing
whose lifecycle you need to track (and Curator depends on a specific
version of ZK), and one more source of bugs.
Not sure it's worth the effort, just my 2c as a Curator user :)

Cheers,

--
Gianmarco


On Thu, Feb 28, 2013 at 11:21 PM, Claudio Martella (JIRA)
<jira@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/GIRAPH-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589996#comment-13589996]
>
> Claudio Martella commented on GIRAPH-540:
> -----------------------------------------
>
> curator is a wrapper client to ZK, hence we'd win in refactor.
>
> > Improved ZooKeeper Library
> > --------------------------
> >
> >                 Key: GIRAPH-540
> >                 URL: https://issues.apache.org/jira/browse/GIRAPH-540
> >             Project: Giraph
> >          Issue Type: Bug
> >            Reporter: Nitay Joffe
> >
> > Look into using https://github.com/Netflix/curator in place of our
> ZooKeeper library. I've heard good things about it. Seems like it could
> simplify a lot of our ZK code.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message