accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1240172 - /incubator/accumulo/site/trunk/content/accumulo/example/wikisearch.mdtext
Date Fri, 03 Feb 2012 13:54:21 GMT
Author: ecn
Date: Fri Feb  3 13:54:21 2012
New Revision: 1240172

add cell borders to tables, fix alignment, add term cardinalities and query result set sizes


Modified: incubator/accumulo/site/trunk/content/accumulo/example/wikisearch.mdtext
--- incubator/accumulo/site/trunk/content/accumulo/example/wikisearch.mdtext (original)
+++ incubator/accumulo/site/trunk/content/accumulo/example/wikisearch.mdtext Fri Feb  3 13:54:21
@@ -33,7 +33,18 @@ The example uses an indexing technique h
 In the example, Accumulo tracks the cardinality of all terms as elements are ingested.  If
the cardinality is small enough, it will track the set of documents by term directly.  For
 <style type="text/css">
-table td,th {padding-right: 10px;}
+table, td, th {
+  padding-right: 5px;
+  padding-left: 5px;
+  border: 1px solid black;
+  border-collapse: collapse;
+td {
+  text-align: right;
+} {
+  text-align: left;
@@ -42,16 +53,16 @@ table td,th {padding-right: 10px;}
 <th colspan="2">Value (count, document list)</th>
-<td align="right">2
-<td>[Document 57, Document 220]
+<td class='lt'>[Document 57, Document 220]
-<td align="right">172849
+<td class='lt'>[]
-<td align="right">1
-<td>[Document 901]
+<td class='lt'>[Document 901]
@@ -99,6 +110,7 @@ The example also creates a reverse word 
 <td>Word, Octopus
 <td>Document 220
 Of course, there would be large numbers of documents in each partition, and the elements
of those documents would be interlaced according to their sort order.
@@ -149,6 +161,7 @@ We performed the following queries, and 
 <th colspan="5">Samples (seconds)
+<th>Result Size
 <td>“old” and “man” and “sea”
@@ -157,6 +170,7 @@ We performed the following queries, and 
 <td>“paris” and “in” and “the” and “spring”
@@ -165,6 +179,7 @@ We performed the following queries, and 
 <td>“rubber” and “duckie” and “ernie”
@@ -173,6 +188,7 @@ We performed the following queries, and 
 <td>“fast”  and ( “furious” or “furriest”) 
@@ -181,6 +197,7 @@ We performed the following queries, and 
 <td>“slashdot” and “grok”
@@ -189,6 +206,7 @@ We performed the following queries, and 
 <td>“three” and “little” and “pigs”
@@ -197,10 +215,35 @@ We performed the following queries, and 
 Because the terms are tested together within the region server, even fairly high-cardinality
terms such as “old,” “man,” and “sea” can be tested efficiently,
without needing to return to the client, or make distributed calls between servers to perform
the intersection between terms.
+For reference, here are the cardinalities for all the terms in the query (remember, this
is across all languages loaded:
+<tr> <th>Term <th> Cardinality
+<tr> <td> ducky <td> 795
+<tr> <td> ernie <td> 13433
+<tr> <td> fast <td> 166813
+<tr> <td> furious <td> 10535
+<tr> <td> furriest <td> 45
+<tr> <td> grok <td> 1168
+<tr> <td> in <td> 1884638
+<tr> <td> little <td> 320748
+<tr> <td> man <td> 548238
+<tr> <td> old <td> 720795
+<tr> <td> paris <td> 232464
+<tr> <td> pigs <td> 8356
+<tr> <td> rubber <td> 17235
+<tr> <td> sea <td> 247231
+<tr> <td> slashdot <td> 2343
+<tr> <td> spring <td> 125605
+<tr> <td> three <td> 718810
 Accumulo supports caching index information, which is turned on by default, and for the non-index
blocks of a file, which is not. After turning on data block caching for the wiki table:

View raw message