[jira] Updated: (ZOOKEEPER-146) Allow clients to retrieve the list of hosts/servers from a URL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-146: -- Assignee: (was: Jakob Homan) Un-assigning myself as it looks like some work is being done and I don't want to appear to be blocking it or such. Will keep watching to see if there is some way I can help out. Allow clients to retrieve the list of hosts/servers from a URL -- Key: ZOOKEEPER-146 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-146 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Fix For: 3.2.0 Attachments: ZOOKEEPER-146.patch As I suggested in ZOOKEEPER-107, it would be nice to allow clients to specify their hosts strings via a URL so that this can change dynamically. For instance, obtain the current list of hosts from a webpage or a file on disk. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-144) add tostring support for watcher event, and enums for event type/state
[ https://issues.apache.org/jira/browse/ZOOKEEPER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-144: -- Status: Patch Available (was: Open) add tostring support for watcher event, and enums for event type/state -- Key: ZOOKEEPER-144 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-144 Project: Zookeeper Issue Type: Improvement Components: java client Reporter: Patrick Hunt Assignee: Jakob Homan Priority: Minor Fix For: 3.0.0 Attachments: ZOOKEEPER-144.patch it would be great if we had toString capability on watcher event, and enums for type/state. the logs would certainly benefit (when fixing this try to update any places where we are logging event information) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-146) Allow clients to retrieve the list of hosts/servers from a URL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635829#action_12635829 ] Jakob Homan commented on ZOOKEEPER-146: --- OK, I wait to see if anything happens with the C version and if so, updated with Patrick's comments at that point. Allow clients to retrieve the list of hosts/servers from a URL -- Key: ZOOKEEPER-146 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-146 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.1.0 Attachments: ZOOKEEPER-146.patch As I suggested in ZOOKEEPER-107, it would be nice to allow clients to specify their hosts strings via a URL so that this can change dynamically. For instance, obtain the current list of hosts from a webpage or a file on disk. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-114) cleanup ugly event messages in zookeeper client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635830#action_12635830
]
Jakob Homan commented on ZOOKEEPER-114:
---
This was fixed in the printing/logging cleanup of ZOOKEEPER-144.
cleanup ugly event messages in zookeeper client
---
Key: ZOOKEEPER-114
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-114
Project: Zookeeper
Issue Type: Improvement
Components: java client
Reporter: Patrick Hunt
Assignee: Jakob Homan
Priority: Trivial
Fix For: 3.0.0
Cleanup the event messages output by the java command line client:
The java client ZooKeeper.java has a process method in MyWatcher that prints
raw event information to the console. Many new users find this confusing (esp
since state changes have a null path).
public void process(WatcherEvent event) {
System.err.println(event.getPath() + : + event.getState() + -
+ event.getType());
}
If this is a state change we should print that, if it's an event we should
print that (state change doesn't have a path). Somewhere in the message we
should also indicate that the client received a watch notification from the
server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-146) Allow clients to retrieve the list of hosts/servers from a URL
Allow clients to retrieve the list of hosts/servers from a URL -- Key: ZOOKEEPER-146 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-146 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 As I suggested in ZOOKEEPER-107, it would be nice to allow clients to specify their hosts strings via a URL so that this can change dynamically. For instance, obtain the current list of hosts from a webpage or a file on disk. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-139) Create Enums for WatcherEvent's KeeperState and EventType
[ https://issues.apache.org/jira/browse/ZOOKEEPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-139: -- Attachment: ZOOKEEPER-139.patch Updated patch to not change the jute code. The Jute type is still WatcherEvent. The type used by users is called WatchedEvent (for lack of any better term). Otherwise the same. Updated to work with changes from ZOOKEEPER-137. Create Enums for WatcherEvent's KeeperState and EventType - Key: ZOOKEEPER-139 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-139 Project: Zookeeper Issue Type: Sub-task Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-139.patch, ZOOKEEPER-139.patch, ZOOKEEPER-139.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-139) Create Enums for WatcherEvent's KeeperState and EventType
[ https://issues.apache.org/jira/browse/ZOOKEEPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-139: -- Status: Patch Available (was: Open) Create Enums for WatcherEvent's KeeperState and EventType - Key: ZOOKEEPER-139 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-139 Project: Zookeeper Issue Type: Sub-task Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-139.patch, ZOOKEEPER-139.patch, ZOOKEEPER-139.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-142: -- Attachment: ZOOKEEPER-142.patch This patch: * Adds verbage to the Javadoc for ZooKeeper.create and ZooKeeper.setData about the 1 mb limit of data in a znode. Also, when I was testing this, I found that passing a large-than-1-mb byte array caused the client to be disconnected, along with the KeeperException being thrown. Is disconnection correct in this case? I'm not sure, just asking. Seems a bit harsh. Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode --- Key: ZOOKEEPER-142 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-142.patch Currently there is nothing in the API documentation as to the maximum size of the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-142: -- Status: Patch Available (was: Open) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode --- Key: ZOOKEEPER-142 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-142.patch Currently there is nothing in the API documentation as to the maximum size of the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-142: -- Priority: Trivial (was: Major) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode --- Key: ZOOKEEPER-142 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Priority: Trivial Fix For: 3.0.0 Attachments: ZOOKEEPER-142.patch Currently there is nothing in the API documentation as to the maximum size of the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-139) Create Enums for WatcherEvent's KeeperState and EventType
Create Enums for WatcherEvent's KeeperState and EventType - Key: ZOOKEEPER-139 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-139 Project: Zookeeper Issue Type: Sub-task Reporter: Jakob Homan Assignee: Jakob Homan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-139) Create Enums for WatcherEvent's KeeperState and EventType
[ https://issues.apache.org/jira/browse/ZOOKEEPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-139: -- Fix Version/s: 3.0.0 Affects Version/s: 3.0.0 Status: Patch Available (was: Open) Create Enums for WatcherEvent's KeeperState and EventType - Key: ZOOKEEPER-139 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-139 Project: Zookeeper Issue Type: Sub-task Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-139.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-132) Create Enum to replace CreateFlag in ZooKepper.create method
[ https://issues.apache.org/jira/browse/ZOOKEEPER-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-132: -- Status: Patch Available (was: Open) Re-did orignal patch per Ben's suggestion. Create Enum to replace CreateFlag in ZooKepper.create method Key: ZOOKEEPER-132 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-132 Project: Zookeeper Issue Type: Sub-task Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-132.patch, ZOOKEEPER-132.patch Replace the current named constant integer in the craete method with a typesafe enum value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-132) Create Enum to replace CreateFlag in ZooKepper.create method
[ https://issues.apache.org/jira/browse/ZOOKEEPER-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-132: -- Attachment: ZOOKEEPER-132.patch OK, per Ben's request the patch now: * Creates an Enum CreateMode that handles all of the possible znode creation combinations * The enum can be converted to/from an int flag for sending over the wire without changing the jute protocol. * The enum provides type-safety and clarity for users, and convenience methods for once it gets to the server * Unit tests for new enum * All the other stuff from above. Again, if this approach looks good, I'll use it for the other constants that need replacing. -jg Create Enum to replace CreateFlag in ZooKepper.create method Key: ZOOKEEPER-132 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-132 Project: Zookeeper Issue Type: Sub-task Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Attachments: ZOOKEEPER-132.patch, ZOOKEEPER-132.patch Replace the current named constant integer in the craete method with a typesafe enum value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-7) Use enums rather than ints for types and state
[ https://issues.apache.org/jira/browse/ZOOKEEPER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan reassigned ZOOKEEPER-7: --- Assignee: Jakob Homan (was: Patrick Hunt) Use enums rather than ints for types and state -- Key: ZOOKEEPER-7 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-7 Project: Zookeeper Issue Type: Bug Components: java client Reporter: Patrick Hunt Assignee: Jakob Homan Priority: Minor Fix For: 3.0.0 Moved from SourceForge to Apache. http://sourceforge.net/tracker/index.php?func=detailaid=1831408group_id=209147atid=1008544 Would be nice to fix in 3.0 as it's a non-bw compat change, also user feedback show's confusion on state/event/missingjavadoc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-132) Create Enum to replace CreateFlag in ZooKepper.create method
Create Enum to replace CreateFlag in ZooKepper.create method Key: ZOOKEEPER-132 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-132 Project: Zookeeper Issue Type: Sub-task Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Replace the current named constant integer in the craete method with a typesafe enum value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-114) cleanup ugly event messages in zookeeper client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan reassigned ZOOKEEPER-114:
-
Assignee: Jakob Homan
cleanup ugly event messages in zookeeper client
---
Key: ZOOKEEPER-114
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-114
Project: Zookeeper
Issue Type: Improvement
Components: java client
Reporter: Patrick Hunt
Assignee: Jakob Homan
Fix For: 3.0.0
Cleanup the event messages output by the java command line client:
The java client ZooKeeper.java has a process method in MyWatcher that prints
raw event information to the console. Many new users find this confusing (esp
since state changes have a null path).
public void process(WatcherEvent event) {
System.err.println(event.getPath() + : + event.getState() + -
+ event.getType());
}
If this is a state change we should print that, if it's an event we should
print that (state change doesn't have a path). Somewhere in the message we
should also indicate that the client received a watch notification from the
server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-123) In two places, the wrong class is specified for the logger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-123: -- Status: Patch Available (was: Open) In two places, the wrong class is specified for the logger -- Key: ZOOKEEPER-123 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-123 Project: Zookeeper Issue Type: Bug Components: java client, tests Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Priority: Minor Attachments: ZOOKEEPER-123.patch Copy and paste strikes again. In two logger instantiations, the wrong class is passed to the constructor. In ClientTest.java and ClientCnxn.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-123) In two places, the wrong class is specified for the logger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-123: -- Attachment: ZOOKEEPER-123.patch Patch replaces the two instances of wrong class names with correct class names. In two places, the wrong class is specified for the logger -- Key: ZOOKEEPER-123 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-123 Project: Zookeeper Issue Type: Bug Components: java client, tests Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Priority: Minor Attachments: ZOOKEEPER-123.patch Copy and paste strikes again. In two logger instantiations, the wrong class is passed to the constructor. In ClientTest.java and ClientCnxn.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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-119) Reserve .zookeeper node for server use.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-119: -- Assignee: Jakob Homan (was: Benjamin Reed) Status: Patch Available (was: Open) 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-119) Reserve .zookeeper node for server use.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-119: -- Attachment: ZOOKEEPER-119.patch D'oh. Slight error in last patch. Ran test twice. Fixed. 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-110) Build script relies on svnant, which is not compatible with subversion 1.5 working copies
[ https://issues.apache.org/jira/browse/ZOOKEEPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-110: -- Attachment: ZOOKEEPER-110.patch Added Apache liecense header to both new files. Build script relies on svnant, which is not compatible with subversion 1.5 working copies - Key: ZOOKEEPER-110 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-110 Project: Zookeeper Issue Type: Bug Components: build Affects Versions: 3.0.0 Environment: Subversion 1.5 command line, or subclipse version 1.4.x Reporter: Jakob Homan Assignee: Jakob Homan Attachments: ZOOKEEPER-110.patch, ZOOKEEPER-110.patch, ZOOKEEPER-110.patch The current build.xml ant script uses svnant to obtain the latest revision number from the repo, however svnant is not compatible with subversion 1.5 (http://subversion.tigris.org/svn_1.5_releasenotes.html), and so the build fails with working copies checked out by this version. The build fails with this version of subversion is too old, please get a newer version... This will become more apparent as svn 1.5 trickles out; I'm using a brand new dev environment with both subclipse 1.4 and svn 1.5 client, so I got bit rather quickly. Those with svn 1.5 can get the code from the trunk, but cannot do an ant build. svnant hasn't been updated in more than a year and appears to be dead, so it may no longer be a viable tool for the ant build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-110) Build script relies on svnant, which is not compatible with subversion 1.5 working copies
[ https://issues.apache.org/jira/browse/ZOOKEEPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-110: -- Attachment: ZOOKEEPER-110.patch OK, I've coded up a DOS batch file that exactly replicates the shell script using only Windows built-in commands, so this fixes the original problem I identified, removes the svnant dependency, adds no new dependencies and will work on Windows natively. Huzzah! I tested it on my OSX, Ubuntu and XP machines and they all worked. Again, the patch doesn't reflect deleting the svnant directory and contents. -jg Build script relies on svnant, which is not compatible with subversion 1.5 working copies - Key: ZOOKEEPER-110 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-110 Project: Zookeeper Issue Type: Bug Components: build Affects Versions: 3.0.0 Environment: Subversion 1.5 command line, or subclipse version 1.4.x Reporter: Jakob Homan Assignee: Jakob Homan Attachments: ZOOKEEPER-110.patch, ZOOKEEPER-110.patch The current build.xml ant script uses svnant to obtain the latest revision number from the repo, however svnant is not compatible with subversion 1.5 (http://subversion.tigris.org/svn_1.5_releasenotes.html), and so the build fails with working copies checked out by this version. The build fails with this version of subversion is too old, please get a newer version... This will become more apparent as svn 1.5 trickles out; I'm using a brand new dev environment with both subclipse 1.4 and svn 1.5 client, so I got bit rather quickly. Those with svn 1.5 can get the code from the trunk, but cannot do an ant build. svnant hasn't been updated in more than a year and appears to be dead, so it may no longer be a viable tool for the ant build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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=12622010#action_12622010 ] Jakob Homan commented on ZOOKEEPER-119: --- Would you also want these to be hidden from/removed from results presented to the getChildren() method, essentially hiding the /.zookeeper from normal client connections? If so, would there then be separate APIs to see it, or would it be completely verboten for client connections? 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: Benjamin Reed 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] 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=12622019#action_12622019 ] Jakob Homan commented on ZOOKEEPER-119: --- Maybe it would work to create the concept of hidden files, ala Linux? Hide the ones that start with dot by default so that all the getChildren calls don't have to have special code to ignore .zookeeper or others. Then create an overloaded getChildren that returns all the hidden files? Just a thought. 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: Benjamin Reed 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] Commented: (ZOOKEEPER-110) Build script relies on svnant, which is not compatible with subversion 1.5 working copies
[ https://issues.apache.org/jira/browse/ZOOKEEPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620368#action_12620368 ] Jakob Homan commented on ZOOKEEPER-110: --- Yes, in the ant exec task you can specify which os the command should run on, so we should be able to write two separate exec tasks: one for win, one for *nix. I'm writing the script for linux now/modifying the buld.xml and will upload the patch in a bit. I can look at how to do it in windows as well, but I'm not sure how to get the info within a good scripting environment. Sorry if it was incorrect to upload the patch that required the bad license. -jg Build script relies on svnant, which is not compatible with subversion 1.5 working copies - Key: ZOOKEEPER-110 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-110 Project: Zookeeper Issue Type: Bug Components: build Affects Versions: 3.0.0 Environment: Subversion 1.5 command line, or subclipse version 1.4.x Reporter: Jakob Homan Assignee: Jakob Homan Attachments: svntask.diff The current build.xml ant script uses svnant to obtain the latest revision number from the repo, however svnant is not compatible with subversion 1.5 (http://subversion.tigris.org/svn_1.5_releasenotes.html), and so the build fails with working copies checked out by this version. The build fails with this version of subversion is too old, please get a newer version... This will become more apparent as svn 1.5 trickles out; I'm using a brand new dev environment with both subclipse 1.4 and svn 1.5 client, so I got bit rather quickly. Those with svn 1.5 can get the code from the trunk, but cannot do an ant build. svnant hasn't been updated in more than a year and appears to be dead, so it may no longer be a viable tool for the ant build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-44) DataTree does not use natural sort for getChildren
[ https://issues.apache.org/jira/browse/ZOOKEEPER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-44: - Attachment: seqfile.diff Implements the changes discussed in the Jira. DataTree does not use natural sort for getChildren -- Key: ZOOKEEPER-44 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-44 Project: Zookeeper Issue Type: Improvement Components: server Affects Versions: 3.0.0 Reporter: Stu Hood Assignee: Benjamin Reed Priority: Minor Fix For: 3.0.0 Attachments: seqfile.diff DataTree.getChildren() performs Collection.sort() on the list of children before returning it, but Java's default comparator for Strings will sort 'lock-20' before 'lock-3' for instance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-44) DataTree does not use natural sort for getChildren
[ https://issues.apache.org/jira/browse/ZOOKEEPER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-44: - Attachment: seqfile2.diff Unnecessary placeholder removed. DataTree does not use natural sort for getChildren -- Key: ZOOKEEPER-44 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-44 Project: Zookeeper Issue Type: Improvement Components: server Affects Versions: 3.0.0 Reporter: Stu Hood Assignee: Jakob Homan Priority: Minor Fix For: 3.0.0 Attachments: seqfile.diff, seqfile2.diff DataTree.getChildren() performs Collection.sort() on the list of children before returning it, but Java's default comparator for Strings will sort 'lock-20' before 'lock-3' for instance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-76) Commit 677109 removed the cobertura library, but not the build targets.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-76: - Status: Patch Available (was: Open) Deletes code coverage build targets Commit 677109 removed the cobertura library, but not the build targets. --- Key: ZOOKEEPER-76 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-76 Project: Zookeeper Issue Type: Bug Components: build Reporter: Jakob Homan Attachments: delcobertura.patch Cobertura library removed due to licensing issues, but the code-coverage ant targets were left in. Have deleted them and created patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
