HBASE-18750 Cleanup the docs saying "HTable use write buffer"
This commit is contained in:
parent
81f05bd943
commit
b646d7249b
|
@ -463,7 +463,7 @@ possible configurations would overwhelm and obscure the important.
|
||||||
<property>
|
<property>
|
||||||
<name>hbase.client.write.buffer</name>
|
<name>hbase.client.write.buffer</name>
|
||||||
<value>2097152</value>
|
<value>2097152</value>
|
||||||
<description>Default size of the HTable client write buffer in bytes.
|
<description>Default size of the BufferedMutator write buffer in bytes.
|
||||||
A bigger buffer takes more memory -- on both the client and server
|
A bigger buffer takes more memory -- on both the client and server
|
||||||
side since server instantiates the passed write buffer to process
|
side since server instantiates the passed write buffer to process
|
||||||
it -- but a larger buffer size reduces the number of RPCs made.
|
it -- but a larger buffer size reduces the number of RPCs made.
|
||||||
|
|
|
@ -217,7 +217,7 @@ Please use link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/C
|
||||||
|
|
||||||
In HBase 1.0 and later, link:http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/client/HTable.html[HTable] is deprecated in favor of link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html[Table]. `Table` does not use autoflush. To do buffered writes, use the BufferedMutator class.
|
In HBase 1.0 and later, link:http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/client/HTable.html[HTable] is deprecated in favor of link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html[Table]. `Table` does not use autoflush. To do buffered writes, use the BufferedMutator class.
|
||||||
|
|
||||||
Before a `Table` or `HTable` instance is discarded, invoke either `close()` or `flushCommits()`, so `Put`s will not be lost.
|
In HBase 2.0 and later, link:http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/client/HTable.html[HTable] does not use BufferedMutator to execute the ``Put`` operation. Refer to link:https://issues.apache.org/jira/browse/HBASE-18500[HBASE-18500] for more information.
|
||||||
|
|
||||||
For additional information on write durability, review the link:/acid-semantics.html[ACID semantics] page.
|
For additional information on write durability, review the link:/acid-semantics.html[ACID semantics] page.
|
||||||
|
|
||||||
|
|
|
@ -279,7 +279,7 @@ Gets are executed via link:http://hbase.apache.org/apidocs/org/apache/hadoop/hba
|
||||||
|
|
||||||
=== Put
|
=== Put
|
||||||
|
|
||||||
link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Put.html[Put] either adds new rows to a table (if the key is new) or can update existing rows (if the key already exists). Puts are executed via link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html#put(org.apache.hadoop.hbase.client.Put)[Table.put] (writeBuffer) or link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html#batch(java.util.List,%20java.lang.Object%5B%5D)[Table.batch] (non-writeBuffer).
|
link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Put.html[Put] either adds new rows to a table (if the key is new) or can update existing rows (if the key already exists). Puts are executed via link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html#put(org.apache.hadoop.hbase.client.Put)[Table.put] (non-writeBuffer) or link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html#batch(java.util.List,%20java.lang.Object%5B%5D)[Table.batch] (non-writeBuffer).
|
||||||
|
|
||||||
[[scan]]
|
[[scan]]
|
||||||
=== Scans
|
=== Scans
|
||||||
|
|
|
@ -620,7 +620,7 @@ Property from ZooKeeper's config zoo.cfg.
|
||||||
*`hbase.client.write.buffer`*::
|
*`hbase.client.write.buffer`*::
|
||||||
+
|
+
|
||||||
.Description
|
.Description
|
||||||
Default size of the HTable client write buffer in bytes.
|
Default size of the BufferedMutator write buffer in bytes.
|
||||||
A bigger buffer takes more memory -- on both the client and server
|
A bigger buffer takes more memory -- on both the client and server
|
||||||
side since server instantiates the passed write buffer to process
|
side since server instantiates the passed write buffer to process
|
||||||
it -- but a larger buffer size reduces the number of RPCs made.
|
it -- but a larger buffer size reduces the number of RPCs made.
|
||||||
|
|
Loading…
Reference in New Issue