[
https://issues.apache.org/jira/browse/HBASE-16489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646232#comment-15646232
]
Enis Soztutar commented on HBASE-16489:
---------------------------------------
bq. HBaseConfiguration is not aware of any SeachPaths, Resources etc. It just
passes the arguments to ConfigurationLoader. I wanted to hide the internals of
ConfigurationLoader from the user, so made ConfigurationLoader a friend of
HBaseConfiguration and not exposed it to the user.
I can see that the implementation just delegates, but we want the path-related
APIs to be in the CL instead of the Configuration object as well. The thinking
is that, if we want to write another non-XML based way to pass configuration
options, then another ConfigurationLoader (like for example
PropertiesConfigurationLoader) class can be written to construct the same
Configuration object.
> Configuration parsing
> ---------------------
>
> Key: HBASE-16489
> URL: https://issues.apache.org/jira/browse/HBASE-16489
> Project: HBase
> Issue Type: Sub-task
> Reporter: Sudeep Sunthankar
> Assignee: Sudeep Sunthankar
> Attachments: HBASE-16489.HBASE-14850.v1.patch,
> HBASE-16489.HBASE-14850.v2.patch, HBASE-16489.HBASE-14850.v3.patch
>
>
> Reading hbase-site.xml is required to read various properties viz.
> zookeeper-quorum, client retires etc. We can either use Apache Xerces or
> Boost libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
