[jira] [Commented] (ZOOKEEPER-1379) 'printwatches, redo, history and connect '. client commands always print usage. This is not necessary

["Edward Ribeiro (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602263#comment-13602263 ] 

Edward Ribeiro commented on ZOOKEEPER-1379:
-------------------------------------------

Hi folks, any interest on commiting this patch? :)
                
> '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.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