[
https://issues.apache.org/jira/browse/ZOOKEEPER-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Ribeiro updated ZOOKEEPER-1379:
--------------------------------------
Attachment: ZOOKEEPER-1379.4.patch
Hi Flávio,
I've cleaned up the trunk patch (ZOOKEEPER-1379.4.patch). I have shrink its
size from 5.3 KB to 2.3 KB by getting rid of unnecessary changes in the file
(mainly involving imports).
Now it's with about the same patch that should be applied to 4.6 branch
(ZOOKEEPER-1379.branch-3.4.patch.
If you or Patrick have any further demand, feel free to say.
Best regards,
Edward
> 'printwatches, redo, history and connect '. client commands always print
> usage. This is not necessary
> -----------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1379
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1379
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
> Affects Versions: 3.4.0, 3.5.0
> Reporter: kavita sharma
> Assignee: Edward Ribeiro
> Priority: Minor
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1379.2.patch, ZOOKEEPER-1379.3.patch,
> ZOOKEEPER-1379.4.patch, ZOOKEEPER-1379.branch-3.4.patch, ZOOKEEPER-1379.patch
>
>
> while executing the commands:
> 'printwatches, redo, history and connect usage is getting print
> .basically we are printing usage if user has entered the command
> wrong but in these commands case every time usage is getting print.
> eg
> {noformat}
> [zk: localhost:2181(CONNECTED) 0] printwatches
> printwatches is on
> ZooKeeper -server host:port cmd args
> connect host:port
> get path [watch]
> ls path [watch]
> set path data [version]
> delquota [-n|-b] path
> quit
> printwatches on|off
> create [-s] [-e] path data acl
> stat path [watch]
> close
> ls2 path [watch]
> history
> listquota path
> setAcl path acl
> getAcl path
> sync path
> redo cmdno
> addauth scheme auth
> delete path [version]
> setquota -n|-b val path
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
