Repository: hbase Updated Branches: refs/heads/branch-1 9c77c55c4 -> c580e4dbd
HBASE-11917 Deprecate / Remove HTableUtil Project: http://git-wip-us.apache.org/repos/asf/hbase/repo Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/c580e4db Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/c580e4db Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/c580e4db Branch: refs/heads/branch-1 Commit: c580e4dbd527541c300e235602f65796589ae102 Parents: 9c77c55 Author: stack <st...@apache.org> Authored: Fri Sep 19 15:59:20 2014 -0700 Committer: stack <st...@apache.org> Committed: Fri Sep 19 15:59:20 2014 -0700 ---------------------------------------------------------------------- .../apache/hadoop/hbase/client/HTableUtil.java | 27 ++++++++++---------- 1 file changed, 14 insertions(+), 13 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hbase/blob/c580e4db/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableUtil.java ---------------------------------------------------------------------- diff --git a/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableUtil.java b/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableUtil.java index 04b3fea..f5a08d2 100644 --- a/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableUtil.java +++ b/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableUtil.java @@ -30,24 +30,25 @@ import java.util.Map; /** * Utility class for HTable. - * * + * @deprecated since 1.0 */ @InterfaceAudience.Private +@Deprecated public class HTableUtil { private static final int INITIAL_LIST_SIZE = 250; - + /** - * Processes a List of Puts and writes them to an HTable instance in RegionServer buckets via the htable.put method. - * This will utilize the writeBuffer, thus the writeBuffer flush frequency may be tuned accordingly via htable.setWriteBufferSize. + * Processes a List of Puts and writes them to an HTable instance in RegionServer buckets via the htable.put method. + * This will utilize the writeBuffer, thus the writeBuffer flush frequency may be tuned accordingly via htable.setWriteBufferSize. * <br><br> * The benefit of submitting Puts in this manner is to minimize the number of RegionServer RPCs in each flush. * <br><br> - * Assumption #1: Regions have been pre-created for the table. If they haven't, then all of the Puts will go to the same region, + * Assumption #1: Regions have been pre-created for the table. If they haven't, then all of the Puts will go to the same region, * defeating the purpose of this utility method. See the Apache HBase book for an explanation of how to do this. * <br> - * Assumption #2: Row-keys are not monotonically increasing. See the Apache HBase book for an explanation of this problem. + * Assumption #2: Row-keys are not monotonically increasing. See the Apache HBase book for an explanation of this problem. * <br> * Assumption #3: That the input list of Puts is big enough to be useful (in the thousands or more). The intent of this * method is to process larger chunks of data. @@ -57,7 +58,7 @@ public class HTableUtil { * @param htable HTable instance for target HBase table * @param puts List of Put instances * @throws IOException if a remote or network exception occurs - * + * */ public static void bucketRsPut(HTable htable, List<Put> puts) throws IOException { @@ -67,17 +68,17 @@ public class HTableUtil { } htable.flushCommits(); } - + /** - * Processes a List of Rows (Put, Delete) and writes them to an HTable instance in RegionServer buckets via the htable.batch method. + * Processes a List of Rows (Put, Delete) and writes them to an HTable instance in RegionServer buckets via the htable.batch method. * <br><br> * The benefit of submitting Puts in this manner is to minimize the number of RegionServer RPCs, thus this will * produce one RPC of Puts per RegionServer. * <br><br> - * Assumption #1: Regions have been pre-created for the table. If they haven't, then all of the Puts will go to the same region, + * Assumption #1: Regions have been pre-created for the table. If they haven't, then all of the Puts will go to the same region, * defeating the purpose of this utility method. See the Apache HBase book for an explanation of how to do this. * <br> - * Assumption #2: Row-keys are not monotonically increasing. See the Apache HBase book for an explanation of this problem. + * Assumption #2: Row-keys are not monotonically increasing. See the Apache HBase book for an explanation of this problem. * <br> * Assumption #3: That the input list of Rows is big enough to be useful (in the thousands or more). The intent of this * method is to process larger chunks of data. @@ -98,7 +99,7 @@ public class HTableUtil { } catch (InterruptedException e) { throw (InterruptedIOException)new InterruptedIOException().initCause(e); } - + } private static Map<String,List<Put>> createRsPutMap(RegionLocator htable, List<Put> puts) throws IOException { @@ -132,5 +133,5 @@ public class HTableUtil { } return rowMap; } - + }
