Author: buildbot
Date: Wed Feb 12 13:16:34 2014
New Revision: 897607

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 13:16:34 2014
@@ -1 +1 @@
-1563028
+1567613

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 
13:16:34 2014
@@ -160,19 +160,22 @@ enables <a href="http://cassandra.apache
 </pre></div>
 
 
-<p>Here you can see that within the keyspace section we specify the Cassandra 
-keyspace schema name Employee, the host localhost and the cluster name 
-Gora Cassandra Test Cluster. Additionally we are required to specify the type 
of 
-column families we wish to create within Cassandra. In this case we create 
three columns; 
-p, f and sc the last of which is further defined as a super column. 
-Further to this, within the Cassandra mappings we are required to specify 
persistent fields 
-which values should map to. In the above example we see that within the class 
element
-the generated class name org.apache.gora.examples.generated.Employee specifies 
the Avro generated
-persistent class, the keyClass java.lang.String which specifies the keys which 
map to the field 
-values and finally the keyspace Employee which matches to the above keyspace 
definition.
-Finally fields which are to be persisted into Cassandra need to be configuired 
such that they 
-receive a name (name, dateOfBirth, ssn and salary respectively), the column 
family 
-to which they belong (all p in this case) and additionally a qualifier, which 
enables 
+<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&lt;&gt;, 
+    the host e.g. <b>localhost&lt;.b&gt;, 
+    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>
 
   </div> <!-- /container (main block) -->


Reply via email to