hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Vigeant (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2006) Documentation of hbase-site.xml parameters
Date Tue, 24 Nov 2009 15:41:39 GMT

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

Mark Vigeant commented on HBASE-2006:

You're absolutely right Stack, and it certainly doesn't make sense to have 2 diverging documentations
that would only serve to make people more confused. I do believe though that the key configurations
need to be more eloquently detailed.

I like your idea Lars, but I'm not sure how to do it since I haven't used XSLT before. It
sounds like it could work though; from the looks of it all the w3 tutorial all it takes is
a XSL stylesheet. 

I think both ideas here are good and potentially very beneficial. I think that I could try
to work on the XSLT transformation but it would require a much more involved committer to
the project to create a more detailed summary of the key configurations (I'm thinking like
how ZooKeeper is documented). Would that be too much of a hassle so early on, or should we
wait until HBase 1.0.0?

> Documentation of hbase-site.xml parameters
> ------------------------------------------
>                 Key: HBASE-2006
>                 URL: https://issues.apache.org/jira/browse/HBASE-2006
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.20.2
>            Reporter: Mark Vigeant
>            Priority: Minor
>         Attachments: hbase_parameters.doc
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> There is nowhere on the site or wiki a detailed examination of the parameters behind
HBase. You have to open hbase-default.xml to see them and their descriptions. A page on the
wiki with descriptions would be nice

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message