Hudson build is back to normal: ZooKeeper-trunk #61
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/61/changes
[jira] Commented: (ZOOKEEPER-119) Reserve .zookeeper node for server use.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12624887#action_12624887 ] Jakob Homan commented on ZOOKEEPER-119: --- That sounds good. With this patch I was just trying to implement Patrick's request and reserve the term for future server use. Reserve .zookeeper node for server use. - Key: ZOOKEEPER-119 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-119 Project: Zookeeper Issue Type: New Feature Components: server Reporter: Patrick Hunt Assignee: Jakob Homan Attachments: ZOOKEEPER-119.patch The server should not allow clients to create .zookeeper nodes in the node hierarchy. These nodes should be reserved for zk future use, some ideas: * /.zookeeper/proc * /.zookeeper/stats * /.zookeeper/... * /.../.zookeeper/... (disallow both at root as well as child nodes) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-38) headers (version+) in log/snap files
[ https://issues.apache.org/jira/browse/ZOOKEEPER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-38: --- Attachment: ZOOKEEPER-38_2.patch here is a patch that applies to the trunk. the last 2 commits made the patch stale. headers (version+) in log/snap files Key: ZOOKEEPER-38 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-38 Project: Zookeeper Issue Type: New Feature Components: server Reporter: Patrick Hunt Assignee: Mahadev konar Fix For: 3.0.0 Attachments: ZOOKEEPER-38.patch, ZOOKEEPER-38.patch, ZOOKEEPER-38.patch, ZOOKEEPER-38_1.patch, ZOOKEEPER-38_2.patch Moved from SourceForge to Apache. http://sourceforge.net/tracker/index.php?func=detailaid=1961767group_id=209147atid=1008547 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
