Author: buildbot
Date: Wed Feb 12 18:30:50 2014
New Revision: 897660
Log:
Staging update by buildbot for gora
Modified:
websites/staging/gora/trunk/content/ (props changed)
websites/staging/gora/trunk/content/current/gora-cassandra.html
Propchange: websites/staging/gora/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 12 18:30:50 2014
@@ -1 +1 @@
-1567710
+1567712
Modified: websites/staging/gora/trunk/content/current/gora-cassandra.html
==============================================================================
--- websites/staging/gora/trunk/content/current/gora-cassandra.html (original)
+++ websites/staging/gora/trunk/content/current/gora-cassandra.html Wed Feb 12
18:30:50 2014
@@ -161,22 +161,40 @@ enables <a href="http://cassandra.apache
<p>Here you can see that we require the definition of two child elements
within the
-<code>gora-orm</code> mapping configuration, namely;
-1. The keyspace element; where we specify:
- the Cassandra keyspace schema name e.g. <b>Employee</b>,
- the host e.g. <b>localhost</b>,
- the Cassandra cluster name e.g. <b>Gora Cassandra Test Cluster</b>,
- the type of column families we wish to create within Cassandra. In this
case we create three columns;
-<b>p</b>, <b>f</b> and <b>sc</b> the last of which is further defined as a
super column.
-2. Specification of persistent fields which values should map to;
- the Persistent class name e.g.
<b>org.apache.gora.examples.generated.Employee</b>,
- the keyClass e.g. <b>java.lang.String</b> which specifies the keys which
map to the field
-values,
- the keyspace e.g. <b>Employee</b> which matches to the above keyspace
definition,
- finally fields which are to be persisted into Cassandra need to be
configured such that they
-receive a <b>name</b> e.g. (name, dateOfBirth, ssn and salary respectively),
the column <b>family</b>
-to which they belong e.g. (all p in this case) and an additional
<b>qualifier</b>, which enables
-more granular control over the data to be persisted into Cassandra.</p>
+<code>gora-orm</code> mapping configuration, namely;</p>
+<p>The <b>keyspace</b> element; where we specify: </p>
+<ol>
+<li>
+<p>a parameter containing the Cassandra keyspace schema name e.g.
<b>Employee</b>, </p>
+</li>
+<li>
+<p>a parameter containing the host e.g. <b>localhost</b>, </p>
+</li>
+<li>
+<p>a parameter containing the Cassandra cluster name e.g. <b>Gora Cassandra
Test Cluster</b>,</p>
+</li>
+<li>
+<p>A nested element containing the name and type of column families we wish to
create within Cassandra. In this case we create three columns; <b>p</b>,
<b>f</b> and <b>sc</b> the last of which contains an optional <b>type</b>
attribute which further defines this as a super column. </p>
+</li>
+</ol>
+<p>The <b>class</b> element specifying persistent fields which values should
map to. This element contains; </p>
+<ol>
+<li>
+<p>a parameter containing the Persistent class name e.g.
<b>org.apache.gora.examples.generated.Employee</b>, </p>
+</li>
+<li>
+<p>a parameter containing the keyClass e.g. <b>java.lang.String</b> which
specifies the keys which map to the field values, </p>
+</li>
+<li>
+<p>a parameter containing the keyspace e.g. <b>Employee</b> which matches to
the above keyspace definition,</p>
+</li>
+<li>
+<p>finally a child element(s) <b>field</b> which represent fields which are to
be persisted into Cassandra. These need to be configured such that they receive
the following;</p>
+<p>a parameter <b>name</b> e.g. (name, dateOfBirth, ssn and salary
respectively), </p>
+<p>a parameter containing the column <b>family</b> to which the field belongs
e.g. (all p in this case), </p>
+<p>an optional parameter <b>qualifier</b>, which enables more granular control
over the data to be persisted into Cassandra.</p>
+</li>
+</ol>
</div> <!-- /container (main block) -->
