anchor.diff:  | Default
   | Description
   
  -| io.hfile.bloom.enabled
  +| io.storefile.bloom.enabled
   | yes
   | Set to no to kill bloom filters server-wide if something goes wrong
   
  -| io.hfile.bloom.error.rate
  +| io.storefile.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.hfile.bloom.max.fold
  +| io.storefile.bloom.max.fold
   | 7
   | The guaranteed maximum fold rate. Changing this setting should not be
                     necessary and is not recommended.
  
positive.code: [[config.bloom]]
  ==== Bloom Filter Configuration
  
  ===== `io.hfile.bloom.enabled` global kill switch
  
  `io.hfile.bloom.enabled` in `Configuration` serves as the kill switch in case something goes wrong.
  Default = `true`.
  
  ===== `io.hfile.bloom.error.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.hfile.bloom.max.fold`
  
  `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.
  
negative.code: | Master switch to enable Delete Family Bloom filters and store them in the StoreFile.
  
  | io.storefile.bloom.block.size
  | 131072
  | Target Bloom block size. Bloom filter blocks of approximately this size
                    are interleaved with data blocks.
  
  