anchor.diff:  ----
   
   [[snappy.compression.installation]]
  -.Install Snappy Support
  -
  -HBase does not ship with Snappy support because of licensing issues.
  -You can install Snappy binaries (for instance, by using +yum install snappy+ on CentOS) or build Snappy from source.
  +.Install Hadoop native Snappy Support
  +
  +Snappy support is bundled with Hadoop and is the default Snappy codec implementation.
  +It is not required that you make use of the Hadoop Snappy codec. Our Snappy codec
  +implemented with Xerial Snappy offers superior performance, and the AirCompressor
  +Snappy codec offers a pure Java option for use where native support is not available.
  +
  +That said, if you prefer the Hadoop codec option, you can install Snappy binaries (for
  +instance, by using +yum install snappy+ on CentOS) or build Snappy from source.
   After installing Snappy, search for the shared library, which will be called _libsnappy.so.X_ where X is a number.
   If you built from source, copy the shared library to a known location on your system, such as _/opt/snappy/lib/_.
   
  
positive.code: See <<brand.new.compressor,brand.new.compressor>>).
  
  [[lzo.compression]]
  .Install LZO Support
  
  HBase cannot ship with LZO because of incompatibility between HBase, which uses an Apache Software License (ASL) and LZO, which uses a GPL license.
  See the link:https://github.com/twitter/hadoop-lzo/blob/master/README.md[Hadoop-LZO at Twitter] for information on configuring LZO support for HBase.
  
  If you depend upon LZO compression, consider configuring your RegionServers to fail to start if LZO is not available.
  See <<hbase.regionserver.codecs,hbase.regionserver.codecs>>.
  
  [[lz4.compression]]
  .Configure LZ4 Support
  
  LZ4 support is bundled with Hadoop.
  Make sure the hadoop shared library (libhadoop.so) is accessible when you start HBase.
  After configuring your platform (see <<hadoop.native.lib,hadoop.native.lib>>), you can make a symbolic link from HBase to the native Hadoop libraries.
  This assumes the two software installs are colocated.
  For example, if my 'platform' is Linux-amd64-64:
  [source,bourne]
  ----
  $ cd $HBASE_HOME
  
negative.code: .Changes Take Effect Upon Compaction
  If you change compression or encoding for a ColumnFamily, the changes take effect during compaction.
  
  Some codecs take advantage of capabilities built into Java, such as GZip compression.
  Others rely on native libraries. Native libraries may be available via codec dependencies installed into
  HBase's library directory, or, if you are utilizing Hadoop codecs, as part of Hadoop. Hadoop codecs
  typically have a native code component so follow instructions for installing Hadoop native binary
  support at <<hadoop.native.lib>>.
  
  This section discusses common codecs that are used and tested with HBase.
  
  No matter what codec you use, be sure to test that it is installed correctly and is available on all nodes in your cluster.
  Extra operational steps may be necessary to be sure that codecs are available on newly-deployed nodes.
  You can use the <<compression.test,compression.test>> utility to check that a given codec is correctly installed.
  