hbase-5408. book.xml, moved "column metadata" section to top-level in Data Model chapter.

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1244681 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Meil 2012-02-15 19:59:28 +00:00
parent db6992f96c
commit b4b62e6d97
1 changed files with 10 additions and 10 deletions

View File

@ -290,16 +290,6 @@ 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>
@ -537,6 +527,16 @@ htable.put(put);
</section>
</section>
</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 as well, 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 xml:id="joins"><title>Joins</title>
<para>Whether HBase supports joins is a common question on the dist-list, and there is a simple answer: it doesn't,
at not least in the way that RDBMS' support them (e.g., with equi-joins or outer-joins in SQL). As has been illustrated