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

Hadoop QA commented on ZOOKEEPER-834:
-------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12495071/ZOOKEEPER-834.patch
  against trunk revision 1172406.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/559//console

This message is automatically generated.

> Allow ephemeral znodes to have children created only by the owner session. 
> ---------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-834
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-834
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: c client, java client, server
>            Reporter: Andrei Savu
>            Assignee: Laxman
>         Attachments: ZOOKEEPER-834.patch
>
>
> Ephemeral znodes are automatically removed when the client session is closed 
> or expires and this behavior makes them very useful when you want to publish 
> status information from active / connected clients. 
> But there is a catch. Right now ephemerals can't have children znodes and 
> because of that clients need to serialize status information as byte strings. 
> This serialization renders that information almost invisible to generic 
> zookeeper clients and hard / inefficient to update. 
> Most of the time the status information can be expressed as a bunch of (key, 
> value) pairs and we could easily store that using child znodes. Any ZooKeeper 
> client can read that info without the need to reverse the serialization 
> process and we can also easily update it. 
> I suggest that the server should allow the ephemeral znodes to have children 
> znodes. Each child should also be an ephemeral znode owned by the same 
> session - parent ephemeralOwner session.
> Mail Archive: 
> http://www.mail-archive.com/[email protected]/msg09819.html
> Another discussion about the same topic:
> http://www.mail-archive.com/[email protected]/msg08165.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to