hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject hbase git commit: HBASE-19182 Add deprecation in branch-1 for hbase-prefix-tree so some heads up it removed in hbase2
Date Tue, 07 Nov 2017 19:30:26 GMT
Repository: hbase
Updated Branches:
  refs/heads/branch-1.3 342328bdd -> 65b23613b

HBASE-19182 Add deprecation in branch-1 for hbase-prefix-tree so some heads up it removed
in hbase2

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

Branch: refs/heads/branch-1.3
Commit: 65b23613b4da801a8c2085a6aa7b02c4f22736fe
Parents: 342328b
Author: Michael Stack <stack@apache.org>
Authored: Sat Nov 4 10:37:10 2017 -0700
Committer: Michael Stack <stack@apache.org>
Committed: Tue Nov 7 11:30:17 2017 -0800

 hbase-prefix-tree/pom.xml                                    | 2 +-
 .../hadoop/hbase/codec/prefixtree/PrefixTreeCodec.java       | 3 +++
 src/main/asciidoc/_chapters/compression.adoc                 | 8 +++++---
 3 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/hbase-prefix-tree/pom.xml b/hbase-prefix-tree/pom.xml
index c6e7aa4..8a6eaf0 100644
--- a/hbase-prefix-tree/pom.xml
+++ b/hbase-prefix-tree/pom.xml
@@ -29,7 +29,7 @@
   <name>Apache HBase - Prefix Tree</name>
-  <description>Prefix Tree Data Block Encoder</description>
+  <description>Prefix Tree Data Block Encoder; DEPRECATED! Removed in hbase-2.0.0</description>

diff --git a/hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/PrefixTreeCodec.java
index a73232f..857c237 100644
--- a/hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/PrefixTreeCodec.java
+++ b/hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/PrefixTreeCodec.java
@@ -57,7 +57,10 @@ import org.apache.hadoop.io.WritableUtils;
  * {@link PrefixTreeEncoder}, and decoding is delegated to instances of
  * {@link org.apache.hadoop.hbase.codec.prefixtree.scanner.CellSearcher}. Encoder and decoder
instances are
  * created and recycled by static PtEncoderFactory and PtDecoderFactory.
+ * @deprecated Since 1.2.7. Will be removed in 2.0.0. Write the dev list if you would like
to take on the
+ * maintainence of this facility.
 public class PrefixTreeCodec implements DataBlockEncoder{

diff --git a/src/main/asciidoc/_chapters/compression.adoc b/src/main/asciidoc/_chapters/compression.adoc
index e5b9b8f..03d7d2e 100644
--- a/src/main/asciidoc/_chapters/compression.adoc
+++ b/src/main/asciidoc/_chapters/compression.adoc
@@ -115,14 +115,16 @@ The data format is nearly identical to Diff encoding, so there is not
an image t
 Prefix Tree::
   Prefix tree encoding was introduced as an experimental feature in HBase 0.96.
   It provides similar memory savings to the Prefix, Diff, and Fast Diff encoder, but provides
faster random access at a cost of slower encoding speed.
 Prefix Tree may be appropriate for applications that have high block cache hit ratios. It
introduces new 'tree' fields for the row and column.
 The row tree field contains a list of offsets/references corresponding to the cells in that
row. This allows for a good deal of compression.
 For more details about Prefix Tree encoding, see link:https://issues.apache.org/jira/browse/HBASE-4676[HBASE-4676].
 It is difficult to graphically illustrate a prefix tree, so no image is included. See the
Wikipedia article for link:http://en.wikipedia.org/wiki/Trie[Trie] for more general information
about this data structure.
+Prefix Tree will be removed in hbase-2.0.0. It is a sweet feature but has seen little uptake
and is not actively maintained.
+Come and write the dev list if you are interesting in carrying-on this encoding.
 === Which Compressor or Data Block Encoder To Use
 The compression or codec type to use depends on the characteristics of your data. Choosing
the wrong type could cause your data to take more space rather than less, and can have performance

View raw message