hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ZOOKEEPER-114) cleanup ugly event messages in zookeeper client
Date Wed, 01 Oct 2008 02:49:46 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Hunt resolved ZOOKEEPER-114.
------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Verified fixed as part of 144 - now have nice logging of events in command line client.

> 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.


Mime
View raw message