[
https://issues.apache.org/jira/browse/HBASE-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699395#comment-13699395
]
stack commented on HBASE-8810:
------------------------------
bq. a file called hbase-settings-sample.xml that would not be included when we
read the conf (while we read hbase-default and hbase-site today). It would be
for documentation only.
We could generate a hbase-default.{html,txt} from hbase-default.xml into conf
dir? Or just put a README.txt into the conf or an xml comment into
hbase-site.template.xml which pointed at the refguide or where to find
hbase-default.xml in src or in jar? This would be less likely to rot in a user
deploy?
bq. a unit test to load this file and compare with the code default, to ensure
our doc is in line with the code.
This is a good idea except except how would it work? How would the unit test
find the code default setting?
> Bring in code constants in line with default xml's
> --------------------------------------------------
>
> Key: HBASE-8810
> URL: https://issues.apache.org/jira/browse/HBASE-8810
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
>
> After the defaults were changed in the xml some constants were left the same.
> DEFAULT_HBASE_CLIENT_PAUSE for example.
--
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
