HBASE-11169 nit: fix incorrect javadoc in OrderedBytes about BlobVar and BlobCopy
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1595389 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
a5f6c55edd
commit
a5cbd502bb
|
@ -98,7 +98,7 @@ import com.google.common.annotations.VisibleForTesting;
|
||||||
* "BlobVar" encodes the input byte[] in a manner similar to a variable length
|
* "BlobVar" encodes the input byte[] in a manner similar to a variable length
|
||||||
* integer encoding. As with the other {@code OrderedBytes} encodings,
|
* integer encoding. As with the other {@code OrderedBytes} encodings,
|
||||||
* the first encoded byte is used to indicate what kind of value follows. This
|
* the first encoded byte is used to indicate what kind of value follows. This
|
||||||
* header byte is 0x35 for BlobVar encoded values. As with the traditional
|
* header byte is 0x37 for BlobVar encoded values. As with the traditional
|
||||||
* varint encoding, the most significant bit of each subsequent encoded
|
* varint encoding, the most significant bit of each subsequent encoded
|
||||||
* {@code byte} is used as a continuation marker. The 7 remaining bits
|
* {@code byte} is used as a continuation marker. The 7 remaining bits
|
||||||
* contain the 7 most significant bits of the first unencoded byte. The next
|
* contain the 7 most significant bits of the first unencoded byte. The next
|
||||||
|
@ -112,7 +112,7 @@ import com.google.common.annotations.VisibleForTesting;
|
||||||
* </p>
|
* </p>
|
||||||
* <h4>BlobCopy</h4>
|
* <h4>BlobCopy</h4>
|
||||||
* <p>
|
* <p>
|
||||||
* "BlobCopy" is a simple byte-for-byte copy of the input data. It uses 0x36
|
* "BlobCopy" is a simple byte-for-byte copy of the input data. It uses 0x38
|
||||||
* as the header byte, and is terminated by 0x00 in the DESCENDING case. This
|
* as the header byte, and is terminated by 0x00 in the DESCENDING case. This
|
||||||
* alternative encoding is faster and more space-efficient, but it cannot
|
* alternative encoding is faster and more space-efficient, but it cannot
|
||||||
* accept values containing a 0x00 byte in DESCENDING order.
|
* accept values containing a 0x00 byte in DESCENDING order.
|
||||||
|
|
Loading…
Reference in New Issue