This is an automated email from the ASF dual-hosted git repository.
kturner pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/fluo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a6f1e97 Jekyll build from gh-pages:a4862db
a6f1e97 is described below
commit a6f1e97787bc618eaf75d75e71d0aa26d07175c0
Author: Keith Turner <ktur...@apache.org>
AuthorDate: Fri Feb 23 12:09:18 2018 -0500
Jekyll build from gh-pages:a4862db
Fix some typos (#125)
---
README.md | 2 +-
blog/2016/05/17/webindex-long-run-2/index.html | 2 +-
docs/fluo-recipes/1.2/recipes/combine-queue.html | 4 ++--
feed.xml | 8 ++++----
release/fluo-1.0.0-alpha-1/index.html | 2 +-
release/fluo-1.2.0/index.html | 1 +
6 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/README.md b/README.md
index 6f4de1b..7ac54ee 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@ a Fluo Recipes release, replace any reference to `fluo` with
`recipes`.
## Create documentation for next release
-Below are steps to create documentaton for the next release of Fluo or Fluo
Recipes. The
+Below are steps to create documentation for the next release of Fluo or Fluo
Recipes. The
directions below are for creating Fluo 1.3 docs from 1.2 docs. For Fluo
Recipes documentation,
replace any reference to `fluo` with `recipes`.
diff --git a/blog/2016/05/17/webindex-long-run-2/index.html
b/blog/2016/05/17/webindex-long-run-2/index.html
index 18e83c6..7f200ae 100644
--- a/blog/2016/05/17/webindex-long-run-2/index.html
+++ b/blog/2016/05/17/webindex-long-run-2/index.html
@@ -158,7 +158,7 @@ that does not last.</p>
<h2 id="cpu-utilization">CPU Utilization</h2>
-<p>Inorder to get higher throughput changes were made to reduce CPU usage and
+<p>In order to get higher throughput changes were made to reduce CPU usage and
evenly spread CPU usage across the cluster. The following plot shows the CPU
usage of all nodes across the cluster during the test. Unfortunately this data
was not kept for the previous run. One issue that caused problems in the
diff --git a/docs/fluo-recipes/1.2/recipes/combine-queue.html
b/docs/fluo-recipes/1.2/recipes/combine-queue.html
index 2b3ce5a..344375a 100644
--- a/docs/fluo-recipes/1.2/recipes/combine-queue.html
+++ b/docs/fluo-recipes/1.2/recipes/combine-queue.html
@@ -230,7 +230,7 @@
cause transactions to fail and throughput to nose dive. For example, consider
<a href="https://github.com/astralway/phrasecount";>phrasecount</a>
which has many transactions processing documents. Each transaction counts the
phrases in a document
and then updates global phrase counts. Since transaction attempts to update
many phrases
-, the probability of collisions is high.</p>
+, the probbaility of collisions is high.</p>
<h2 id="solution">Solution</h2>
@@ -417,7 +417,7 @@ calls <code class="highlighter-rouge">process()</code> on a
<a href="https://sta
<ul>
<li>The new value reported for an update will be derived from combining all
-updates that were committed before the transaction thats processing updates
+updates that were committed before the transaction that’s processing updates
started. The implementation may have to make multiple passes over queued
updates to achieve this. In the situation where TX1 queues a <code
class="highlighter-rouge">+1</code> and later
TX2 queues a <code class="highlighter-rouge">-1</code> for the same key, there
is no need to worry about only seeing
diff --git a/feed.xml b/feed.xml
index 7b92151..1580fb4 100644
--- a/feed.xml
+++ b/feed.xml
@@ -2,11 +2,11 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom";>
<channel>
<title>Apache Fluo</title>
- <description>Mirror of Apache Fluo Website</description>
+ <description>Mirror of Apache Fluo Website (Incubator)</description>
<link>https://fluo.apache.org//</link>
<atom:link href="https://fluo.apache.org//feed.xml"; rel="self"
type="application/rss+xml" />
- <pubDate>Thu, 11 Jan 2018 22:46:01 +0000</pubDate>
- <lastBuildDate>Thu, 11 Jan 2018 22:46:01 +0000</lastBuildDate>
+ <pubDate>Fri, 23 Feb 2018 17:09:12 +0000</pubDate>
+ <lastBuildDate>Fri, 23 Feb 2018 17:09:12 +0000</lastBuildDate>
<generator>Jekyll v3.6.2</generator>
@@ -1160,7 +1160,7 @@ that does not last.</p>
<h2 id="cpu-utilization">CPU Utilization</h2>
-<p>Inorder to get higher throughput changes were made to reduce CPU
usage and
+<p>In order to get higher throughput changes were made to reduce CPU
usage and
evenly spread CPU usage across the cluster. The following plot shows the CPU
usage of all nodes across the cluster during the test. Unfortunately this data
was not kept for the previous run. One issue that caused problems in the
diff --git a/release/fluo-1.0.0-alpha-1/index.html
b/release/fluo-1.0.0-alpha-1/index.html
index 031608a..c0fd91e 100644
--- a/release/fluo-1.0.0-alpha-1/index.html
+++ b/release/fluo-1.0.0-alpha-1/index.html
@@ -143,7 +143,7 @@
<h4 id="garbage-collection">Garbage Collection</h4>
-<p>Without garbage collection, the columnns in a Fluo table would grow without
bound as updates are applied over time. Because of this, it’s important to
clean up old fully-processed (and no longer being read) transaction data. The
initial implementation of garbage collection kept N versions of columns. <a
href="https://github.com/fluo-io/fluo/issues/8";>Fluo-8</a> added the ability to
garbage collect all column versions that are no longer being read by
transactions anywhere else in the c [...]
+<p>Without garbage collection, the columns in a Fluo table would grow without
bound as updates are applied over time. Because of this, it’s important to
clean up old fully-processed (and no longer being read) transaction data. The
initial implementation of garbage collection kept N versions of columns. <a
href="https://github.com/fluo-io/fluo/issues/8";>Fluo-8</a> added the ability to
garbage collect all column versions that are no longer being read by
transactions anywhere else in the cl [...]
<h4 id="mapreduce-inputformat">MapReduce InputFormat</h4>
diff --git a/release/fluo-1.2.0/index.html b/release/fluo-1.2.0/index.html
index 9683807..5c8a734 100644
--- a/release/fluo-1.2.0/index.html
+++ b/release/fluo-1.2.0/index.html
@@ -171,6 +171,7 @@ refactoring has the following notable changes:</p>
<li>Code for launching Fluo applications in YARN was moved to its <a
href="https://github.com/apache/fluo-yarn";>own project</a> that has its own
<a href="https://fluo.apache.org/release/fluo-yarn-1.0.0";>release</a> tarball.
The Fluo tarball can still be used to launch Fluo applications
in YARN if a <code class="highlighter-rouge">fluo.properties</code> is created
from <code class="highlighter-rouge">fluo.properties.deprecated</code>.</li>
+ <li>Fluo application jars are now stored in HDFS and application
configuration is now stored in Zookeeper. This information used to be stored
in a local directory. This change made running Fluo different ways (like YARN
or Docker) possible.</li>
</ul>
<p>Read the <a
href="https://fluo.apache.org/docs/fluo/1.2/getting-started/quick-start";>quickstart
documentation</a> to learn how to run Fluo applications using these new
methods.</p>
--
To stop receiving notification emails like this one, please contact
ktur...@apache.org.
