curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-120) NodeCache and PathChildrenCache should not perform writes
Date Thu, 10 Jul 2014 17:40:06 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057718#comment-14057718
] 

Scott Blum commented on CURATOR-120:
------------------------------------

Ah, rats.  We're somewhat new to Curator.  My team is trying to switch all/most of our ZK
related code over to Curator and push for internal adoption, and this was a blocker for another
team.  They want their observers to be truly read-only and not push any writes into ZK at
all, and they want to be able to watch a non-existent tree and get notified when it comes
into existence.


> NodeCache and PathChildrenCache should not perform writes
> ---------------------------------------------------------
>
>                 Key: CURATOR-120
>                 URL: https://issues.apache.org/jira/browse/CURATOR-120
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Scott Blum
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> NodeCache and PathChildrenCache should act as read-only views of data.  Unnecessarily,
both of them forcibly create the node being watched.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message