hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16489) Configuration parsing
Date Wed, 16 Nov 2016 23:59:58 GMT

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

Enis Soztutar commented on HBASE-16489:

Also for constant names, in Java we sometimes use all caps, sometimes not. I personally do
not like all caps at all since I think it reduces readability. Googles style guide recommends
to name all constants with a prefix of {{k}} and camel-case: 
https://google.github.io/styleguide/cppguide.html#Constant_Names. HDFS also uses this convention
it seems. Let's use that going forward. We can fix the existing code retroactively in another

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