[jira] [Commented] (BOOKKEEPER-197) HedwigConsole uses the same file to load bookkeeper client config and hub server config

["Sijie Guo (Commented) (JIRA)" <ji...@apache.org>]

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

Sijie Guo commented on BOOKKEEPER-197:
--------------------------------------

hmm, actually hub server is a bookkeeper client. when hub server runs, it would load server cfg file as ServerConfiguration for hub server, and as ClientConfiguration for bookkeeper client. since hedwig console is an admin tool for a hub server, it works as what hub server does. 

I think the problem here is hub server uses a flat key/value configuration file, it lacks the ability to group properties into sections (said hub server settings in hub server section, bookkeeper client settings to bookeeper section) to avoid option name confliction. (although option name confliction would not happen now, since bookkeeper uses camel word for option name, while hedwig doesn't)
                
> HedwigConsole uses the same file to load bookkeeper client config and hub server config
> ---------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-197
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-197
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>    Affects Versions: 4.1.0
>            Reporter: Aniruddha
>            Priority: Minor
>
> In the current implementation of HedwigConsole.java, The same server-cfg file (default = hedwig-server/conf/hw_server.conf) is used to load both hubServerConf and bkClientConf. This seems incorrect because both have different option names. 

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