hbase-5406 book.xml - adding section to Data Model chapter about column metadata.
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1244676 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
87d4ad6980
commit
db6992f96c
|
@ -175,6 +175,8 @@
|
|||
<literal>t6</literal>, the value of <varname>anchor:cnnsi.com</varname>
|
||||
from time stamp <literal>t9</literal>, the value of
|
||||
<varname>anchor:my.look.ca</varname> from time stamp <literal>t8</literal>.
|
||||
</para>
|
||||
<para>For more information about the internals of how HBase stores data, see <xref linkend="regions.arch" />.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
|
@ -288,6 +290,16 @@ try {
|
|||
</para>
|
||||
|
||||
</section>
|
||||
<section xml:id="dm.column.metadata">
|
||||
<title>Column Metadata</title>
|
||||
<para>There is no store of column metadata outside of the internal KeyValue instances for a ColumnFamily.
|
||||
Thus, while HBase can support not only a wide number of columns per row, but a heterogenous set of columns
|
||||
between rows, it is your responsibility to keep track of the column names.
|
||||
</para>
|
||||
<para>The only way to get a complete set of columns that exist for a ColumnFamily is to process all the rows.
|
||||
For more information about how HBase stores data internally, see <xref linkend="keyvalue" />.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
</section>
|
||||
|
||||
|
|
Loading…
Reference in New Issue