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

Hudson commented on HBASE-4786:
-------------------------------

Integrated in HBase-TRUNK #2439 (See 
[https://builds.apache.org/job/HBase-TRUNK/2439/])
    HBASE-4786 book.xml,performance.xml adding and reorg of schema info

dmeil : 
Files : 
* /hbase/trunk/src/docbkx/book.xml
* /hbase/trunk/src/docbkx/performance.xml

                
> [book] adding and reorganizing schema design information
> --------------------------------------------------------
>
>                 Key: HBASE-4786
>                 URL: https://issues.apache.org/jira/browse/HBASE-4786
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Doug Meil
>            Assignee: Doug Meil
>            Priority: Minor
>         Attachments: docbkx_HBASE_4786.patch
>
>
> Adding more schema design information.  Consolidated the "performance" 
> related schema options in the performance chapter so there wouldn't be 
> explanations of these concepts in both the Schema Design chapter and also the 
> Performance chapter.
> book.xml
> * schema design chapter: moved the in-memory CF option, and bloom filter to 
> the Peformance chapter's schema design section.  
> * added link to performance chapter schema design section in Schema Design 
> chapter.
> * added comment that online schema changes will be available in .92 (for an 
> example where it shows a table being disabled for a CF change)
> performance.xml
> * added the in-memory CF option and bloom filter reference from book.xml (see 
> above)
> * added sub-section on per-table regionsize configuration.
> * added subsection on blocksize configuration.
> * clarified entry on regionsizes and made it clear that large 20gb regions 
> are only for HFile v2 format, whereas the largest HFile v1 format region is 
> somewhere around 4gb.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to