Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of charlie.mas@gmail.com
 designates 209.85.218.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:date:message-id:subject:from:to:content-type;
        b=Q+eKsTjwiUkijEKtEGUf+mNyDCKjILorc8ciILE/gaoyDu0Zkl3YCzRsrNngvoxWJ1
         Gf52RzFEUnre9k0ku4cJEvqyqiM/uvo5UpVp/vQWEfC+xVkUuKNIhO+WL0TNPuT2vvGE
         QcJTMvHbrBcK6l/Q0SU/hQe+9jPPnMh2sq2Hs=
MIME-Version: 1.0
Reply-To: charlie.mas@gmail.com
Date: Sun, 21 Mar 2010 22:07:45 +0000
Message-ID: <1960fb141003211507x5e070e7bqadb38ed1aef48db0@mail.gmail.com>
Subject: Announcing OCM - The Object Cassandra Mapper
From: Charlie Mason <charlie.mas@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

I am going to be using Cassandra for a project I am working on. To
enable me to use it more easily I have built a relatively simple ORM
to simplify access to Cassandra and to provide some extra
functionality. When I say ORM I am not talking about developing a
Hibernate for Cassandra, OCM is much more light weight than that and
tailored to the Cassandra data model.

It has a simple Specification file format that defines how you want to
map your data to objects in your chosen programming language.  This is
then fed into the OCM complier which generates a series of human
readable source files in the specified language. This combined with
base OCM library can be used by your app. It also generates the
storage-config.xml file for you.

Currently there is only a Java backend for the OCM complier, although
it should be relatively straight forward to add support for other
languages as all the code generation is done form simple Velocity
templates. The Java backend uses the Hector library to interface with
Cassandra and so benefits from load balancing and connection pooling.

OCM has a few extra features on top of basic CRUD style persistence:

Any column can be marked as Indexed. OCM automatically maintains a
secondary table mapping the column to the key of parent Column Family.
Changes made through OCM automatically update the index. It also
provides a static method in the Java language to obtain a row using
the indexed field e.g. usersByEmail for a standard user table with the
user id as the key.

Many2Many relationships can also be defined. These are implemented as
a Supper Column in both tables. OCM maintains both of these
automatically as and when they are updated or removed.

The Range Scanner provides a simple interface to obtain records by
scanning a accross a number of keys. It splits the range scan into a
number of range slice calls, so you can gradually progress through
very large scan ranges just be asking for the next row form OCM.


Its available under the Apache license on Git Hub.

http://github.com/charliem/OCM

Let me know what you think or if you have any questions. Contributions
are more than welcome if anyone else is interested in using it. Its
still a bit rough around the edges although most of the basic
functionality is working, at least for Java apps.


Charlie M