HBASE-3764 Book.xml - adding 2 FAQs (SQL and arch question)
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1091290 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
f616c0c709
commit
afa5418210
|
@ -148,6 +148,7 @@ Release 0.91.0 - Unreleased
|
||||||
coprocessor collection
|
coprocessor collection
|
||||||
HBASE-3729 Get cells via shell with a time range predicate
|
HBASE-3729 Get cells via shell with a time range predicate
|
||||||
(Ted Yu via Stack)
|
(Ted Yu via Stack)
|
||||||
|
HBASE-3764 Book.xml - adding 2 FAQs (SQL and arch question)
|
||||||
|
|
||||||
TASK
|
TASK
|
||||||
HBASE-3559 Move report of split to master OFF the heartbeat channel
|
HBASE-3559 Move report of split to master OFF the heartbeat channel
|
||||||
|
|
|
@ -1235,6 +1235,26 @@ false
|
||||||
</para>
|
</para>
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
<qandaentry xml:id="faq.sql">
|
||||||
|
<question><para>Does HBase support SQL?</para></question>
|
||||||
|
<answer>
|
||||||
|
<para>
|
||||||
|
Not really. SQL-ish support for HBase via <link xlink:href="http://hive.apache.org/">Hive</link> is in development, however Hive is based on MapReduce which is not generally suitable for low-latency requests.
|
||||||
|
See the <link linkend="datamodel">Data Model</link> section for examples on the HBase client.
|
||||||
|
</para>
|
||||||
|
</answer>
|
||||||
|
</qandaentry>
|
||||||
|
<qandaentry xml:id="faq.hdfs.hbase">
|
||||||
|
<question><para>How does HBase work on top of HDFS?</para></question>
|
||||||
|
<answer>
|
||||||
|
<para>
|
||||||
|
<link xlink:href="http://hadoop.apache.org/hdfs/">HDFS</link> is a distributed file system that is well suited for the storage of large files. It's documentation
|
||||||
|
states that it is not, however, a general purpose file system, and does not provide fast individual record lookups in files.
|
||||||
|
HBase, on the other hand, is built on top of HDFS and provides fast record lookups (and updates) for large tables. This can sometimes be a point of conceptual confusion.
|
||||||
|
See the <link linkend="datamodel">Data Model</link> and <link linkend="architecture">Architecture</link> sections for more information on how HBase achieves its goals.
|
||||||
|
</para>
|
||||||
|
</answer>
|
||||||
|
</qandaentry>
|
||||||
<qandaentry xml:id="brand.new.compressor">
|
<qandaentry xml:id="brand.new.compressor">
|
||||||
<question><para>Why are logs flooded with '2011-01-10 12:40:48,407 INFO org.apache.hadoop.io.compress.CodecPool: Got
|
<question><para>Why are logs flooded with '2011-01-10 12:40:48,407 INFO org.apache.hadoop.io.compress.CodecPool: Got
|
||||||
brand-new compressor' messages?</para></question>
|
brand-new compressor' messages?</para></question>
|
||||||
|
|
Loading…
Reference in New Issue