[
https://issues.apache.org/jira/browse/ZOOKEEPER-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113342#comment-13113342
]
[email protected] commented on ZOOKEEPER-834:
---------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2037/
-----------------------------------------------------------
Review request for zookeeper, Patrick Hunt, Benjamin Reed, and Mahadev Konar.
Summary
-------
Allow ephemeral znodes to have children created only by the owner session.
This addresses bug ZOOKEEPER-834.
https://issues.apache.org/jira/browse/ZOOKEEPER-834
Diffs
-----
./src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml 1173537
./src/java/main/org/apache/zookeeper/KeeperException.java 1173537
./src/java/main/org/apache/zookeeper/ZooKeeperMain.java 1173537
./src/java/main/org/apache/zookeeper/server/DataTree.java 1173537
./src/java/main/org/apache/zookeeper/server/PrepRequestProcessor.java 1173537
./src/java/test/org/apache/zookeeper/test/EphemeralNodeTest.java PRE-CREATION
Diff: https://reviews.apache.org/r/2037/diff
Testing
-------
Patch includes tests for different scenarios. Passing in qa bot.
Thanks,
Laxman
> 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
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-834.1.patch, ZOOKEEPER-834.2.patch,
> 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
