Cassandra Terminology : Cheat Sheet


*This document will be updated continuously until it is as complete as can be, please let me know what I can add to make it more useful for everyone, especially new Cassandra  users*

Columns

At the bottom end of the hierarchy there is a column, a column has three parts to it; A name, value and a timestamp. The name and value is stored as a raw byte array (byte[]) and can be of any size.

Super Columns

A super column is similar in terms of having a name,value pair however, it does not have a timestamp.

The major difference between a column and a super column is that :

A column maps to the binary representation of a string value and a super column maps to a number of columns. Read more of this post

Cassandra Query Language (CQL) v2.0 reference


This is an update to my two previous posts:
http://crlog.info/2011/03/29/cassandra-query-language-aka-cql-syntax/ AND
http://crlog.info/2011/06/13/cassandra-query-language-cql-v1-0-0-updated/
If you’re using versions of Cassandra prior v1.0 beta one of the above links may be more appropriate as little things may have changed here and there. The official doc is on Gitub in textile markup here https://github.com/apache/cassandra/blob/trunk/doc/cql/CQL.textile

Cassandra Query Language (CQL) v2.0

Read more of this post

CQL : Creating a simple keyspace


I promised a few tutorials covering CQL examples so I’m going to kick off a series to demonstrate all/most of the features of Cassandra‘s new query language, CQL.

In this example we’ll create a keyspace and look at the proerties available when doing so, this will demonstrate one of the key words in CQL, CREATE KEYSPACE. This example has been done in Java since it is one of the easiest languages to get up and running with, however the CQL statements are portable i.e. not dependent on the language you use. There is a PHP CQL driver being developed by Nick, Dave, my self and others but I’ve been out for about a month pre-occupied with a few things, the guys have been making some progress so check out the driver if you’re using PHP and want to use or contribute to the development. Read more of this post

Apache Cassandra + PHPcassa + Code Igniter = large scale PHP app in 5 minutes


I’m working on a new project, migrating an existing site using custom code with a very monolithic design on top of MySQL.

Design goals : Implement all the same functionality using a manageable framework with a small footprint on a distributed NoSQL database.
Small footprint? I’m thinking Code Igniter (CI)… Distributed NoSQL (my favorite part)? I’m thinking Apache Cassandra!!!
First problem…issue, whatever you want to call it. CI is built with SQL DB tied in fairly tightly. How do I separate the two without hacking the CI core and allow me to have the flexibility of upgrading CI in the future? And at the same time being able to integrate Cassandra tightly enough to not make it stand out like a penguin in Africa  sore thumb?

Enough with the questions, I’m very new to CI so this took me about an hour to make it happen. The idea is, CI provides a $this->db object when “database” is one of the auto loaded options. I want to still have this db instance available but providing  methods to access Cassandra. I also want this to be auto loaded and available in all controllers… So how? Read more of this post

Follow

Get every new post delivered to your Inbox.

Join 351 other followers

%d bloggers like this: