[fluo-website] branch gh-pages updated: Update 2017-09-22-fluo-1.2.0.md (#124)

[mw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mwalch pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/fluo-website.git


The following commit(s) were added to refs/heads/gh-pages by this push:
     new 80cf4c5  Update 2017-09-22-fluo-1.2.0.md (#124)
80cf4c5 is described below

commit 80cf4c5d9a0842377fb72d9138e12a3f7a72e041
Author: Keith Turner <ke...@deenlo.com>
AuthorDate: Fri Jan 12 16:34:14 2018 -0500

    Update 2017-09-22-fluo-1.2.0.md (#124)
---
 _posts/release/2017-09-22-fluo-1.2.0.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/_posts/release/2017-09-22-fluo-1.2.0.md b/_posts/release/2017-09-22-fluo-1.2.0.md
index c97cdcd..31db51b 100644
--- a/_posts/release/2017-09-22-fluo-1.2.0.md
+++ b/_posts/release/2017-09-22-fluo-1.2.0.md
@@ -38,6 +38,7 @@ refactoring has the following notable changes:
 * Code for launching Fluo applications in YARN was moved to its [own project][fluo-yarn] that has its own
   [release][fluo-yarn-release] tarball. The Fluo tarball can still be used to launch Fluo applications
   in YARN if a `fluo.properties` is created from `fluo.properties.deprecated`.
+* 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.
 
 Read the [quickstart documentation][quickstart] to learn how to run Fluo applications using these new methods.
 

-- 
To stop receiving notification emails like this one, please contact
['"commits@fluo.apache.org" <co...@fluo.apache.org>'].