You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2012/05/30 17:25:23 UTC

[jira] [Created] (BOOKKEEPER-276) Add commandline options so that Hedwig console doesn't have to use config files

Ivan Kelly created BOOKKEEPER-276:
-------------------------------------

             Summary: Add commandline options so that Hedwig console doesn't have to use config files
                 Key: BOOKKEEPER-276
                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-276
             Project: Bookkeeper
          Issue Type: Bug
            Reporter: Ivan Kelly
             Fix For: 4.2.0


Hedwig console currently requires a number of config files to find the cluster. Really it should be sufficient to give it a zookeeper server and let it go from there. Also, it would be good to be able to run hedwig console commands from the commandline. 
i.e. bin/hedwig console --zookeeper zk1:2181 show topics



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BOOKKEEPER-276) Add commandline options so that Hedwig console doesn't have to use config files

Posted by "Ivan Kelly (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BOOKKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-276:
----------------------------------

    Fix Version/s:     (was: 4.2.0)
                   4.3.0
    
> Add commandline options so that Hedwig console doesn't have to use config files
> -------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-276
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-276
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>             Fix For: 4.3.0
>
>
> Hedwig console currently requires a number of config files to find the cluster. Really it should be sufficient to give it a zookeeper server and let it go from there. Also, it would be good to be able to run hedwig console commands from the commandline. 
> i.e. bin/hedwig console --zookeeper zk1:2181 show topics

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

[jira] [Commented] (BOOKKEEPER-276) Add commandline options so that Hedwig console doesn't have to use config files

Posted by "Sijie Guo (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BOOKKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285777#comment-13285777 ] 

Sijie Guo commented on BOOKKEEPER-276:
--------------------------------------

Actually, hedwig console supports run commands from the commandline like 'bin/hedwig console show topics'.

Agreed to add some commandline options. e.g. zookeeper option.
                
> Add commandline options so that Hedwig console doesn't have to use config files
> -------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-276
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-276
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>             Fix For: 4.2.0
>
>
> Hedwig console currently requires a number of config files to find the cluster. Really it should be sufficient to give it a zookeeper server and let it go from there. Also, it would be good to be able to run hedwig console commands from the commandline. 
> i.e. bin/hedwig console --zookeeper zk1:2181 show topics

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira