Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-14994 Clean up some broken links and references to old APIs

This commit is contained in:
Misty Stanley-Jones 2015-12-16 11:28:57 -08:00
parent 7099ab4c56
commit 6a0159046e
3 changed files with 16 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/main/asciidoc/_chapters/appendix_hfile_format.adoc
View File

@ -225,7 +225,7 @@ In contrast with version 1, in a version 2 HFile Bloom filter metadata is stored
==== File Info format in versions 1 and 2
The file info block is a serialized link:http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/io/HbaseMapWritable.html[HbaseMapWritable] (essentially a map from byte arrays to byte arrays) with the following keys, among others.
The file info block is a serialized map from byte arrays to byte arrays, with the following keys, among others.
StoreFile-level logic adds more keys to this.
[cols="1,1", frame="all"]
@ -235,9 +235,11 @@ StoreFile-level logic adds more keys to this.
|hfile.AVG_VALUE_LEN| The average value length in the file (int)
|===
File info format did not change in version 2.
However, we moved the file info to the final section of the file, which can be loaded as one block at the time the HFile is being opened.
Also, we do not store comparator in the version 2 file info anymore.
In version 2, we did not change the file format, but we moved the file info to
the final section of the file, which can be loaded as one block when the HFile
is being opened.
Also, we do not store the comparator in the version 2 file info anymore.
Instead, we store it in the fixed file trailer.
This is because we need to know the comparator at the time of parsing the load-on-open section of the HFile.

4
src/main/asciidoc/_chapters/hbase-default.adoc
View File

@ -1248,7 +1248,9 @@ When the size of a leaf-level, intermediate-level, or root-level
+
.Description
Where to store the contents of the bucketcache. One of: onheap,
offheap, or file. If a file, set it to file:PATH_TO_FILE. See https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html for more information.
offheap, or file. If a file, set it to file:PATH_TO_FILE.
See https://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html
for more information.
+
.Default

9
src/main/asciidoc/_chapters/schema_design.adoc
View File

@ -632,8 +632,13 @@ For more information, see <<coprocessors,coprocessors>>
== Constraints
HBase currently supports 'constraints' in traditional (SQL) database parlance.
The advised usage for Constraints is in enforcing business rules for attributes in the table (e.g. make sure values are in the range 1-10). Constraints could also be used to enforce referential integrity, but this is strongly discouraged as it will dramatically decrease the write throughput of the tables where integrity checking is enabled.
Extensive documentation on using Constraints can be found at: link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/constraint[Constraint] since version 0.94.
The advised usage for Constraints is in enforcing business rules for attributes
in the table (e.g. make sure values are in the range 1-10). Constraints could
also be used to enforce referential integrity, but this is strongly discouraged
as it will dramatically decrease the write throughput of the tables where integrity
checking is enabled. Extensive documentation on using Constraints can be found at
link:http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/constraint/Constraint.html[Constraint]
since version 0.94.
[[schema.casestudies]]
== Schema Design Case Studies