hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudeep Sunthankar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16489) Configuration parsing
Date Sat, 19 Nov 2016 12:34:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15679187#comment-15679187

Sudeep Sunthankar commented on HBASE-16489:

Ok, but we cannot even assume that the machine running the unit test will have /etc/hbase/conf
directory created. Better to confine everything under temp directories in build/test-data.


Our unit tests don't refer /etc/hbase/conf anywhere. It is only used as a default search path
by the library to load hbase-default.xml or hbase-site.xml.

> 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, HBASE-16489.HBASE-14850.v4.patch, HBASE-16489.HBASE-14850.v5.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

View raw message