hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bus...@apache.org
Subject [1/2] hbase git commit: Revert "Correct Bloom filter documentation in the book (yi liang)"
Date Fri, 29 Apr 2016 13:34:19 GMT
Repository: hbase
Updated Branches:
  refs/heads/master 470630318 -> cd148b7ce


Revert "Correct Bloom filter documentation in the book (yi liang)"

This reverts commit 31b85e73da8bee80e8aa918de09fd85d1d7a724a.

Bad commit message.


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/547398ec
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/547398ec
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/547398ec

Branch: refs/heads/master
Commit: 547398eccdab5af853f5bc02ec6c5fc1e7799c18
Parents: 4706303
Author: Sean Busbey <busbey@apache.org>
Authored: Fri Apr 29 08:33:09 2016 -0500
Committer: Sean Busbey <busbey@apache.org>
Committed: Fri Apr 29 08:33:09 2016 -0500

----------------------------------------------------------------------
 src/main/asciidoc/_chapters/performance.adoc | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/547398ec/src/main/asciidoc/_chapters/performance.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/_chapters/performance.adoc b/src/main/asciidoc/_chapters/performance.adoc
index efb6ace..b37fd5f 100644
--- a/src/main/asciidoc/_chapters/performance.adoc
+++ b/src/main/asciidoc/_chapters/performance.adoc
@@ -366,7 +366,7 @@ Bloom filters need to be rebuilt upon deletion, so may not be appropriate
in env
 
 Bloom filters are enabled on a Column Family.
 You can do this by using the setBloomFilterType method of HColumnDescriptor or using the
HBase API.
-Valid values are `NONE`, `ROW` (default), or `ROWCOL`.
+Valid values are `NONE` (the default), `ROW`, or `ROWCOL`.
 See <<bloom.filters.when>> for more information on `ROW` versus `ROWCOL`.
 See also the API documentation for link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HColumnDescriptor.html[HColumnDescriptor].
 
@@ -387,17 +387,17 @@ You can configure the following settings in the _hbase-site.xml_.
 | Default
 | Description
 
-| io.storefile.bloom.enabled
+| io.hfile.bloom.enabled
 | yes
 | Set to no to kill bloom filters server-wide if something goes wrong
 
-| io.storefile.bloom.error.rate
+| io.hfile.bloom.error.rate
 | .01
 | The average false positive rate for bloom filters. Folding is used to
                   maintain the false positive rate. Expressed as a decimal representation
of a
                   percentage.
 
-| io.storefile.bloom.max.fold
+| io.hfile.bloom.max.fold
 | 7
 | The guaranteed maximum fold rate. Changing this setting should not be
                   necessary and is not recommended.
@@ -411,7 +411,7 @@ You can configure the following settings in the _hbase-site.xml_.
 | Master switch to enable Delete Family Bloom filters and store them in the StoreFile.
 
 | io.storefile.bloom.block.size
-| 131072
+| 65536
 | Target Bloom block size. Bloom filter blocks of approximately this size
                   are interleaved with data blocks.
 
@@ -718,20 +718,20 @@ Stored in the LRU cache, if it is enabled (It's enabled by default).
 [[config.bloom]]
 ==== Bloom Filter Configuration
 
-===== `io.storefile.bloom.enabled` global kill switch
+===== `io.hfile.bloom.enabled` global kill switch
 
-`io.storefile.bloom.enabled` in `Configuration` serves as the kill switch in case something
goes wrong.
+`io.hfile.bloom.enabled` in `Configuration` serves as the kill switch in case something goes
wrong.
 Default = `true`.
 
-===== `io.storefile.bloom.error.rate`
+===== `io.hfile.bloom.error.rate`
 
-`io.storefile.bloom.error.rate` = average false positive rate.
+`io.hfile.bloom.error.rate` = average false positive rate.
 Default = 1%. Decrease rate by ½ (e.g.
 to .5%) == +1 bit per bloom entry.
 
-===== `io.storefile.bloom.max.fold`
+===== `io.hfile.bloom.max.fold`
 
-`io.storefile.bloom.max.fold` = guaranteed minimum fold rate.
+`io.hfile.bloom.max.fold` = guaranteed minimum fold rate.
 Most people should leave this alone.
 Default = 7, or can collapse to at least 1/128th of original size.
 See the _Development Process_ section of the document link:https://issues.apache.org/jira/secure/attachment/12444007/Bloom_Filters_in_HBase.pdf[BloomFilters
in HBase] for more on what this option means.


Mime
View raw message