Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # dev >> Work on CLI


Hi,

i started to look into the CLI code of zookeeper, and think of making some
contributions there.

My ideas:
- use commons-cli for option parsing (see:
ZOOKEEPER-271<https://issues.apache.org/jira/browse/ZOOKEEPER-271>
)
- switch to options instead of args: like -w instead of [watch] or -v
version instead of [version]
- use a -s option if you want to see Stat of a command
- we could also do a "rm [-r]" instead of "delete" and "deleteall" (see:
ZOOKEEPER-1326 <https://issues.apache.org/jira/browse/ZOOKEEPER-1326>)
- order the result of a "ls" command
- order the list of available commands
- introduce own Class for every command, to be more flexible in adding
removing commands

To you think this could be a valid contribution to the project?
What about compatibility? Is it important that all the "current" commands
work in the same way?
Some changes (like introducing [-v version] or [-w])  will not be backward
compatible.

Any comments welcome.

/Hartmut
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB