Layer of goodness on top of the Cassandra Ruby Driver so you do not have to write CQL strings all over the place.
Add this line to your application's Gemfile:
gem 'cassanity'
require 'cassanity'
# client does the heavy lifting of setting up a cassandra cql database instance,
# a cassanity executor for that database, and a cassanity connection
client = Cassanity::Client.new
# get keyspace instance
keyspace = client[:my_app]
# tell client to use keyspace for future queries
# this is optional as cassanity always sends the keyspace and column family name
# whenever they are needed
keyspace.use
# schema for apps column family
apps_schema = Cassanity::Schema.new({
primary_key: :id,
columns: {
id: :text,
name: :text,
created_at: :timestamp,
},
with: {
comment: 'For storing apps',
}
})
# get instance of column family with name and schema set
apps = keyspace.column_family({
name: :apps,
schema: apps_schema,
})
# you can also just pass a hash for the schema
apps = keyspace.column_family({
name: :apps,
schema: {
primary_key: :id,
columns: {
id: :text,
name: :text,
created_at: :timestamp,
},
with: {
comment: 'For storing apps',
}
},
})
# create column family based on name and schema
apps.create
# insert row
apps.insert(data: {
id: '1',
name: 'GitHub.com',
created_at: Time.now,
})
# update name for row
apps.update(set: {name: 'GitHub'}, where: {id: '1'})
# delete row
apps.delete(where: {id: '1'})
# truncate column family (remove all rows, still can add new stuff)
apps.truncate
# drop column family (no more inserting into it, it is gone)
apps.dropYou can also do a lot more. Here are a few more examples:
- Ruby >= 1.9.3
- Cassandra >= 1.2 with CQL >= 3.1.0
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request