Author: buildbot Date: Fri Jul 18 15:29:11 2014 New Revision: 916683 Log: Staging update by buildbot for gora
Modified: websites/staging/gora/trunk/content/ (props changed) websites/staging/gora/trunk/content/current/gora-core.html Propchange: websites/staging/gora/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Jul 18 15:29:11 2014 @@ -1 +1 @@ -1611378 +1611671 Modified: websites/staging/gora/trunk/content/current/gora-core.html ============================================================================== --- websites/staging/gora/trunk/content/current/gora-core.html (original) +++ websites/staging/gora/trunk/content/current/gora-core.html Fri Jul 18 15:29:11 2014 @@ -155,22 +155,39 @@ under the License. <div class="container" id="Gora_Gora Core Module"> -<h2 id="overview">Overview</h2> -<p>This is the main documentation for the gora-core module. gora-core -holds most of the core functionality for the gora project. Every module -in gora depends on gora-core. Therefore most of the generic documentation -about the project is gathered here as well as the documentation for AvroStore, -DataFileAvroStore and MemStore. In addition to this gora-core holds all of the -core MapReduce, Persistency, Query and Base DataStore and Utility functionality -which is also documented here.</p> +<h1 id="overview">Overview</h1> +<p>This is the main documentation for DataStore's contained within the +<code>gora-core</code> module which (as it's name implies) +holds most of the core functionality for the gora project. </p> +<p>Every module +in gora depends on gora-core therefore most of the generic documentation +about the project is gathered here as well as the documentation for <code>AvroStore</code>, +<code>DataFileAvroStore</code> and <code>MemStore</code>. In addition to this, gora-core holds all of the +core <strong>MapReduce</strong>, <strong>Persistency</strong>, <strong>Query</strong>, <strong>DataStoreBase</strong> and <strong>Utility</strong> functionality.</p> <div class="toc"> <ul> <li><a href="#overview">Overview</a></li> +<li><a href="#avrostore">AvroStore</a><ul> <li><a href="#goraproperties">gora.properties</a></li> <li><a href="#to-configure-the-datafileavrostore-one-would-typically-set-the-following">To configure the DataFileAvroStore one would typically set the following:</a></li> <li><a href="#gora-core-mappings">Gora Core mappings</a></li> </ul> +</li> +<li><a href="#avrostore_1">AvroStore</a><ul> +<li><a href="#goraproperties_1">gora.properties</a></li> +<li><a href="#to-configure-the-datafileavrostore-one-would-typically-set-the-following_1">To configure the DataFileAvroStore one would typically set the following:</a></li> +<li><a href="#gora-core-mappings_1">Gora Core mappings</a></li> +</ul> +</li> +<li><a href="#avrostore_2">AvroStore</a><ul> +<li><a href="#goraproperties_2">gora.properties</a></li> +<li><a href="#to-configure-the-datafileavrostore-one-would-typically-set-the-following_2">To configure the DataFileAvroStore one would typically set the following:</a></li> +<li><a href="#gora-core-mappings_2">Gora Core mappings</a></li> +</ul> +</li> +</ul> </div> +<h1 id="avrostore">AvroStore</h1> <h2 id="goraproperties">gora.properties</h2> <p>To configure the AvroStore one would typically set the following: <em> gora.avrostore.output.path=hdfs://uri/path/to/hdfs/data/directory || file:///uri/path/to/local/data/directory - This value should point to the hdfs data directory (if running Gora in a distributed Hadoop environment) or to some location on the local file system (if running Gora locally). @@ -184,6 +201,34 @@ which is also documented here.</p> * gora.memstore.xxx=xxx - xyz</p> <h2 id="gora-core-mappings">Gora Core mappings</h2> <p>In the stores covered within the gora-core module, no physical mappings are required.</p> +<h1 id="avrostore_1">AvroStore</h1> +<h2 id="goraproperties_1">gora.properties</h2> +<p>To configure the AvroStore one would typically set the following: +<em> gora.avrostore.output.path=hdfs://uri/path/to/hdfs/data/directory || file:///uri/path/to/local/data/directory - This value should point to the hdfs data directory (if running Gora in a distributed Hadoop environment) or to some location on the local file system (if running Gora locally). +</em> gora.avrostore.xxx=xxx - xyz</p> +<h2 id="to-configure-the-datafileavrostore-one-would-typically-set-the-following_1">To configure the DataFileAvroStore one would typically set the following:</h2> +<ul> +<li>gora.datafileavrostore.xxx=xxx - xyz </li> +<li>gora.datafileavrostore.xxx=xxx - xyz</li> +</ul> +<p>To configure the MemStore one would typically set the following: +* gora.memstore.xxx=xxx - xyz</p> +<h2 id="gora-core-mappings_1">Gora Core mappings</h2> +<p>In the stores covered within the gora-core module, no physical mappings are required.</p> +<h1 id="avrostore_2">AvroStore</h1> +<h2 id="goraproperties_2">gora.properties</h2> +<p>To configure the AvroStore one would typically set the following: +<em> gora.avrostore.output.path=hdfs://uri/path/to/hdfs/data/directory || file:///uri/path/to/local/data/directory - This value should point to the hdfs data directory (if running Gora in a distributed Hadoop environment) or to some location on the local file system (if running Gora locally). +</em> gora.avrostore.xxx=xxx - xyz</p> +<h2 id="to-configure-the-datafileavrostore-one-would-typically-set-the-following_2">To configure the DataFileAvroStore one would typically set the following:</h2> +<ul> +<li>gora.datafileavrostore.xxx=xxx - xyz </li> +<li>gora.datafileavrostore.xxx=xxx - xyz</li> +</ul> +<p>To configure the MemStore one would typically set the following: +* gora.memstore.xxx=xxx - xyz</p> +<h2 id="gora-core-mappings_2">Gora Core mappings</h2> +<p>In the stores covered within the gora-core module, no physical mappings are required.</p> </div> <!-- /container (main block) -->