HBASE-3844 Book.xml (removing link to defunct wiki) and Performance.xml (adding client tip)

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1098721 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2011-05-02 18:35:49 +00:00
parent 2a4f052bcc
commit 3ad05c6aac
2 changed files with 11 additions and 2 deletions

View File

@ -1322,8 +1322,7 @@ false
<answer>
<para>
See the FAQ that is up on the wiki, <link xlink:href="http://wiki.apache.org/hadoop/Hbase/FAQ">HBase Wiki FAQ</link>
as well as the <link xlink:href="http://wiki.apache.org/hadoop/Hbase/Troubleshooting">Troubleshooting</link> page and
the <link xlink:href="http://wiki.apache.org/hadoop/Hbase/FrequentlySeenErrors">Frequently Seen Errors</link> page.
as well as the <link xlink:href="http://wiki.apache.org/hadoop/Hbase/Troubleshooting">Troubleshooting</link> page.
</para>
</answer>
</qandaentry>

View File

@ -189,6 +189,16 @@ public static byte[][] getHexSplits(String startKey, String endKey, int numRegio
have the cache value be large because it costs more in memory for both
client and RegionServer, so bigger isn't always better.</para>
</section>
<section xml:id="perf.hbase.client.selection">
<title>Scan Attribute Selection</title>
<para>Whenever a Scan is used to process large numbers of rows (and especially when used
as a MapReduce source), be aware of which attributes are selected. If <code>scan.addFamily</code> is called
then <emphasis>all</emphasis> of the attributes in the specified ColumnFamily will be returned to the client.
If only a small number of the available attributes are to be processed, then only those attributes should be specified
in the input scan because attribute over-selection is a non-trivial performance penalty over large datasets.
</para>
</section>
<section xml:id="perf.hbase.client.scannerclose">
<title>Close ResultScanners</title>