You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by mu...@apache.org on 2014/06/05 21:27:22 UTC
svn commit: r1600735 - in /phoenix/site: publish/ source/src/site/markdown/
Author: mujtaba
Date: Thu Jun 5 19:27:22 2014
New Revision: 1600735
URL: http://svn.apache.org/r1600735
Log:
PHOENIX-1024 Fix typos
Modified:
phoenix/site/publish/bulk_dataload.html
phoenix/site/publish/contributing.html
phoenix/site/publish/faq.html
phoenix/site/publish/recent.html
phoenix/site/publish/secondary_indexing.html
phoenix/site/publish/tuning.html
phoenix/site/source/src/site/markdown/bulk_dataload.md
phoenix/site/source/src/site/markdown/contributing.md
phoenix/site/source/src/site/markdown/faq.md
phoenix/site/source/src/site/markdown/recent.md
phoenix/site/source/src/site/markdown/secondary_indexing.md
phoenix/site/source/src/site/markdown/tuning.md
Modified: phoenix/site/publish/bulk_dataload.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/bulk_dataload.html?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/publish/bulk_dataload.html (original)
+++ phoenix/site/publish/bulk_dataload.html Thu Jun 5 19:27:22 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2014-06-03
+ Generated by Apache Maven Doxia at 2014-06-05
Rendered using Reflow Maven Skin 1.1.0 (http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -273,7 +273,7 @@
2,3:4,5
</pre>
</div>
- <p>To load this file, the default delimiter (comma) would be used, and the array delimiter (colon) would be supplied with the parametr <tt>-a ':'</tt>.</p>
+ <p>To load this file, the default delimiter (comma) would be used, and the array delimiter (colon) would be supplied with the parameter <tt>-a ':'</tt>.</p>
</div>
</div>
</div>
Modified: phoenix/site/publish/contributing.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/contributing.html?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/publish/contributing.html (original)
+++ phoenix/site/publish/contributing.html Thu Jun 5 19:27:22 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2014-06-04
+ Generated by Apache Maven Doxia at 2014-06-05
Rendered using Reflow Maven Skin 1.1.0 (http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -135,7 +135,7 @@
<p>These steps are explained in greater detail below.</p>
<div class="section">
<h3 id="Discuss_on_the_mailing_list">Discuss on the mailing list</h3>
- <p>Itâs often best to discuss a change on the public mailing lists before creating and sumbitting a patch.</p>
+ <p>Itâs often best to discuss a change on the public mailing lists before creating and submitting a patch.</p>
<p>If youâre unsure whether certain behavior in Phoenix is a bug, please send a mail to the <a href="mailing_list.html">user mailing list</a> to check.</p>
<p>If youâre considering adding major new functionality to Phoenix, itâs a good idea to first discuss the idea on the <a href="mailing_list.html">developer mailing list</a> to make sure that your plans are in line with others in the Phoenix community.</p>
</div>
Modified: phoenix/site/publish/faq.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/faq.html?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/publish/faq.html (original)
+++ phoenix/site/publish/faq.html Thu Jun 5 19:27:22 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2014-06-03
+ Generated by Apache Maven Doxia at 2014-06-05
Rendered using Reflow Maven Skin 1.1.0 (http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -250,7 +250,7 @@ public class test {
</ul>
<p>Column family contains related data in separate files. If you query use selected columns then it make sense to group those columns together in a column family to improve read performance.</p>
<p>Example:</p>
- <p>Following create table DDL will create two column familes A and B.</p>
+ <p>Following create table DDL will create two column faimiles A and B.</p>
<p><tt>CREATE TABLE TEST (MYKEY VARCHAR NOT NULL PRIMARY KEY, A.COL1 VARCHAR, A.COL2 VARCHAR, B.COL3 VARCHAR)</tt></p>
<ul>
<li>Use <b>compression</b> On disk compression improves performance on large tables</li>
Modified: phoenix/site/publish/recent.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/recent.html?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/publish/recent.html (original)
+++ phoenix/site/publish/recent.html Thu Jun 5 19:27:22 2014
@@ -129,7 +129,7 @@
<li><b><a href="views.html">Views</a></b>. Allows the creation of multiple tables using the same physical HBase table. <b>Available in our 3.0/4.0 release</b></li>
<li><b><a href="multi-tenancy.html">Multi-tenancy</a></b>. Allows independent views to be created by different tenants on a per-connection basis that all share the same physical HBase table. <b>Available in our 3.0/4.0 release</b></li>
<li><b><a href="sequences.html">Sequences</a></b>. Support for CREATE/DROP SEQUENCE, NEXT VALUE FOR, and CURRENT VALUE FOR has been implemented. <b>Available in our 3.0/4.0 release</b></li>
- <li><b><a href="array_type.html">ARRAY Type</a></b>. Suppport for the standard JDBC ARRAY type. <b>Available in our 3.0/4.0 release</b></li>
+ <li><b><a href="array_type.html">ARRAY Type</a></b>. Support for the standard JDBC ARRAY type. <b>Available in our 3.0/4.0 release</b></li>
<li><b><a href="secondary_indexing.html">Secondary Indexes</a></b>. Allows users to create indexes over mutable or immutable data through a new <tt>CREATE INDEX</tt> DDL command. Behind the scenes, Phoenix creates a separate HBase table with a different row key for the index. At query time, Phoenix takes care of choosing the best table to use based on how much of the row key can be formed. We support getting at the uncommitted <tt>List<KeyValue></tt> for both the data and the index tables to allow an HFile to be built without needing an HBase connection using the âconnectionlessâ of our JDBC driver.</li>
<li><b><a href="paged.html">Paged Queries</a></b>. Paged queries through row value constructors, a standard SQL construct to efficiently locate the row at or after a composite key value. Enables a query-more capability to efficiently step through your data and optimizes IN list of composite key values to be point gets.</li>
<li><b><a href="bulk_dataload.html">CSV Bulk Loader</a></b>. Bulk load CSV files into HBase either through map-reduce or a client-side script.</li>
Modified: phoenix/site/publish/secondary_indexing.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/secondary_indexing.html?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/publish/secondary_indexing.html (original)
+++ phoenix/site/publish/secondary_indexing.html Thu Jun 5 19:27:22 2014
@@ -267,7 +267,7 @@
<p>We track secondary index performance via our <a class="externalLink" href="http://phoenix-bin.github.io/client/performance/latest.htm">performance framework</a>. This is a generic test of performance based on defaults - your results will vary based on hardware specs as well as you individual configuration.</p>
<p>That said, we have seen secondary indexing (both immutable and mutable) go as quickly as < 2x the regular write path on a small, (3 node) desktop-based cluster. This is actually a phenomenal as we have to write to multiple tables as well as build the index update.</p>
<h1>Presentations</h1>
- <p>There have been several presentations given on how secondary indexing works in Phoenix that have a more indepth look at how indexing works (with pretty pictures!):</p>
+ <p>There have been several presentations given on how secondary indexing works in Phoenix that have a more in-depth look at how indexing works (with pretty pictures!):</p>
<ul>
<li><a class="externalLink" href="http://files.meetup.com/1350427/PhoenixIndexing-SF-HUG_09-26-13.pptx">San Francisco HBase Meetup</a> - Sept. 26, 2013</li>
<li><a class="externalLink" href="http://www.slideshare.net/jesse_yates/phoenix-secondary-indexing-la-hug-sept-9th-2013">Los Anglees HBase Meetup</a> - Sept, 4th, 2013</li>
Modified: phoenix/site/publish/tuning.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/tuning.html?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/publish/tuning.html (original)
+++ phoenix/site/publish/tuning.html Thu Jun 5 19:27:22 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2014-06-04
+ Generated by Apache Maven Doxia at 2014-06-05
Rendered using Reflow Maven Skin 1.1.0 (http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -158,7 +158,7 @@
</tr>
<tr class="a">
<td><small>phoenix.query.maxSpoolToDiskBytes</small></td>
- <td style="text-align: left;">Threshold size in bytes upto which results from parallelly executed query results are spooled to disk above which the query will fail. Default is 1 gb.</td>
+ <td style="text-align: left;">Threshold size in bytes up to which results from parallelly executed query results are spooled to disk above which the query will fail. Default is 1 gb.</td>
<td>1024000000</td>
</tr>
<tr class="b">
Modified: phoenix/site/source/src/site/markdown/bulk_dataload.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/bulk_dataload.md?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/bulk_dataload.md (original)
+++ phoenix/site/source/src/site/markdown/bulk_dataload.md Thu Jun 5 19:27:22 2014
@@ -84,4 +84,4 @@ Both the PSQL loader and MapReduce loade
1,2:3:4
2,3:4,5
-To load this file, the default delimiter (comma) would be used, and the array delimiter (colon) would be supplied with the parametr `-a ':'`.
+To load this file, the default delimiter (comma) would be used, and the array delimiter (colon) would be supplied with the parameter `-a ':'`.
Modified: phoenix/site/source/src/site/markdown/contributing.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/contributing.md?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/contributing.md (original)
+++ phoenix/site/source/src/site/markdown/contributing.md Thu Jun 5 19:27:22 2014
@@ -13,7 +13,7 @@ These steps are explained in greater det
### Discuss on the mailing list
-It's often best to discuss a change on the public mailing lists before creating and sumbitting a patch.
+It's often best to discuss a change on the public mailing lists before creating and submitting a patch.
If you're unsure whether certain behavior in Phoenix is a bug, please send a mail to the [user mailing list](mailing_list.html) to check.
Modified: phoenix/site/source/src/site/markdown/faq.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/faq.md?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/faq.md (original)
+++ phoenix/site/source/src/site/markdown/faq.md Thu Jun 5 19:27:22 2014
@@ -169,7 +169,7 @@ Column family contains related data in s
Example:
-Following create table DDL will create two column familes A and B.
+Following create table DDL will create two column faimiles A and B.
` CREATE TABLE TEST (MYKEY VARCHAR NOT NULL PRIMARY KEY, A.COL1 VARCHAR, A.COL2 VARCHAR, B.COL3 VARCHAR)`
Modified: phoenix/site/source/src/site/markdown/recent.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/recent.md?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/recent.md (original)
+++ phoenix/site/source/src/site/markdown/recent.md Thu Jun 5 19:27:22 2014
@@ -6,7 +6,7 @@ As items are implemented from our road m
2. **[Views](views.html)**. Allows the creation of multiple tables using the same physical HBase table. **Available in our 3.0/4.0 release**
3. **[Multi-tenancy](multi-tenancy.html)**. Allows independent views to be created by different tenants on a per-connection basis that all share the same physical HBase table. **Available in our 3.0/4.0 release**
2. **[Sequences](sequences.html)**. Support for CREATE/DROP SEQUENCE, NEXT VALUE FOR, and CURRENT VALUE FOR has been implemented. **Available in our 3.0/4.0 release**
-4. **[ARRAY Type](array_type.html)**. Suppport for the standard JDBC ARRAY type. **Available in our 3.0/4.0 release**
+4. **[ARRAY Type](array_type.html)**. Support for the standard JDBC ARRAY type. **Available in our 3.0/4.0 release**
1. **[Secondary Indexes](secondary_indexing.html)**. Allows users to create indexes over mutable or immutable data through a new `CREATE INDEX` DDL command. Behind the scenes, Phoenix creates a separate HBase table with a different row key for the index. At query time, Phoenix takes care of choosing the best table to use based on how much of the row key can be formed. We support getting at the uncommitted <code>List<KeyValue></code> for both the data and the index tables to allow an HFile to be built without needing an HBase connection using the "connectionless" of our JDBC driver.
2. **[Paged Queries](paged.html)**. Paged queries through row value constructors, a standard SQL construct to efficiently locate the row at or after a composite key value. Enables a query-more capability to efficiently step through your data and optimizes IN list of composite key values to be point gets.
3. **[CSV Bulk Loader](bulk_dataload.html)**. Bulk load CSV files into HBase either through map-reduce or a client-side script.
Modified: phoenix/site/source/src/site/markdown/secondary_indexing.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/secondary_indexing.md?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/secondary_indexing.md (original)
+++ phoenix/site/source/src/site/markdown/secondary_indexing.md Thu Jun 5 19:27:22 2014
@@ -150,7 +150,7 @@ We track secondary index performance via
That said, we have seen secondary indexing (both immutable and mutable) go as quickly as < 2x the regular write path on a small, (3 node) desktop-based cluster. This is actually a phenomenal as we have to write to multiple tables as well as build the index update.
# Presentations
-There have been several presentations given on how secondary indexing works in Phoenix that have a more indepth look at how indexing works (with pretty pictures!):
+There have been several presentations given on how secondary indexing works in Phoenix that have a more in-depth look at how indexing works (with pretty pictures!):
* [San Francisco HBase Meetup](http://files.meetup.com/1350427/PhoenixIndexing-SF-HUG_09-26-13.pptx) - Sept. 26, 2013
* [Los Anglees HBase Meetup](http://www.slideshare.net/jesse_yates/phoenix-secondary-indexing-la-hug-sept-9th-2013) - Sept, 4th, 2013
Modified: phoenix/site/source/src/site/markdown/tuning.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/tuning.md?rev=1600735&r1=1600734&r2=1600735&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/tuning.md (original)
+++ phoenix/site/source/src/site/markdown/tuning.md Thu Jun 5 19:27:22 2014
@@ -30,7 +30,7 @@ of the
size in bytes after which results from parallelly executed
query results are spooled to disk. Default is 20 mb.</td><td>20971520</td></tr>
<tr><td><small>phoenix.query.maxSpoolToDiskBytes</small></td><td style="text-align: left;">Threshold
- size in bytes upto which results from parallelly executed
+ size in bytes up to which results from parallelly executed
query results are spooled to disk above which the query will fail. Default is 1 gb.</td><td>1024000000</td></tr>
<tr><td><small>phoenix.query.maxGlobalMemoryPercentage</small></td><td style="text-align: left;">Percentage of total heap memory (i.e. Runtime.getRuntime().maxMemory()) that all threads may use. Only course grain memory usage is tracked, mainly accounting for memory usage in the intermediate map built during group by aggregation. When this limit is reached the clients block attempting to get more memory, essentially throttling memory usage. Defaults to 15%</td><td>15</td></tr>
<tr><td><small>phoenix.query.maxGlobalMemorySize</small></td><td style="text-align: left;">Max size in bytes of total tracked memory usage. By default not specified, however, if present, the lower of this parameter and the phoenix.query.maxGlobalMemoryPercentage will be used