diff --git a/src/main/docbkx/schema_design.xml b/src/main/docbkx/schema_design.xml index 40afefce39a..65e64b0c45b 100644 --- a/src/main/docbkx/schema_design.xml +++ b/src/main/docbkx/schema_design.xml @@ -513,20 +513,34 @@ public static byte[][] getHexSplits(String startKey, String endKey, int numRegio
Keeping Deleted Cells - ColumnFamilies can optionally keep deleted cells. That means deleted cells can still be - retrieved with By default, delete markers extend back to the beginning of time. Therefore, Get or Scan - operations, as long these operations have a time range specified that ends before the - timestamp of any delete that would affect the cells. This allows for point in time queries - even in the presence of deletes. + operations will not see a deleted cell (row or column), even when the Get or Scan operation + indicates a time range + before the delete marker was placed. + ColumnFamilies can optionally keep deleted cells. In this case, deleted cells can still be + retrieved, as long as these operations specify a time range that ends before the timestamp of + any delete that would affect the cells. This allows for point-in-time queries even in the + presence of deletes. Deleted cells are still subject to TTL and there will never be more than "maximum number of versions" deleted cells. A new "raw" scan options returns all deleted rows and the delete markers. - See HColumnDescriptor - for more information. + + Change the Value of <code>KEEP_DELETED_CELLS</code> Using HBase Shell + hbase> hbase> alter ‘t1′, NAME => ‘f1′, KEEP_DELETED_CELLS => true + + + Change the Value of <code>KEEP_DELETED_CELLS</code> Using the API + ... +HColumnDescriptor.setKeepDeletedCells(true); +... + + + See the API documentation for KEEP_DELETED_CELLS for more information.