cassmap 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 3ac34ccacfc5d09afe56514f7fa60de8d37bb315
+  data.tar.gz: 7f3d63ea8ea0982f74dec94f2aa45bfc7d268ca5
+SHA512:
+  metadata.gz: 6ac974dc98013fc333025b39dce7ea5d356d9ebbb6a11378cdade208340a4490bf04d7edd7b57a00615d2b258b1ec945dce596bc082788277ee7aa62c9f9ef0a
+  data.tar.gz: 1ae4a8e1a5d02a34a9259099333fce324087e0ff0378cdfcfb0f8388f6d4a7fb1859e274eafe9217f07195ef10d8f62bb0a0cb6f444629b9e45a6ee7dec817ab

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,8 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in cassmap.gemspec
+gemspec
+
+group :development do
+  gem 'guard-rspec', require: false
+end

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2014 Ryan Svihla
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,108 @@
+# Cassmap
+
+<p><b>Consider this pre-alpha and use at your own risk. This will take at least a month to not suck.</b></p>
+
+<p>Cassmap provides ActiveRecord like functionality with <b>full query table tracking</b> for those on Rails wishing to use
+    the excellent Cassandra distributed data store.
+</p>
+
+#What's query table tracking?
+
+<p>Good Cassandra data modeling embraces the distributed nature of the database, and makes heavy use of
+materialized views or as I like to refer to them "Query Tables". In this concept you denormalize your data
+and model your tables after the queries you need to preform in your application. Denormalization of course has
+downsides when it comes to data consistency and performance if you're making roundtrips for each table.
+</p>
+
+<p>Cassandra's api helps us solve the data consistency between query tables problem with the BATCH statment. Other
+Active Record implmentations do not allow you to batch these updates easily and most people resort to hand CQL and respositories
+to keep their data consisten. I aim to eliminate this boilerplate.</p>
+
+## Usage
+
+### ActiveModel Implementation
+
+I'm aiming to be as compatible as possible with ActiveRecord's in syntax, I do not believe this will be 100%
+possible
+
+In the simplest case, given a model that looks like this:
+
+    class Trade < Cassmap::Base
+        add_query_table :trades_by_price
+    end
+
+and two tables that look like this:
+
+    CREATE TABLE trades ( id timeuuid, price decimal, quantity int, symbol text, PRIMARY KEY(id));
+    CREATE TABLE trades_by_price ( id timeuuid, price decimal, quantity int, symbol text, PRIMARY KEY(price));
+
+and client code that looks like this:
+
+    #returns all trades with a price of
+    Trade.where( price: 100.00)
+
+    #saves data to all related query tables
+    #Trade.create( price: 100.00, quantity: 10, symbol: 'AA', id: UUID.timestamp_create )
+
+<p>In more complex cases Cassmap knows when there are columns missing, and knows when there is
+
+#### Pending important features
+
+* Dirty Tracking
+* Callback support
+* Ability to apply transforms on query tables where columns are stored in a different format or is a combination of values
+* Smarter handling of Where. What to do if you have two keys that overlap?
+
+### Migrations support
+
+<p>Typical Rails rule apply. Time format, followed by a file name that matches the class name.
+
+    #file named 2014_01_23_11_43_98_add_trades_by_minute_table_migration.rb
+    class AddTradesByMinuteTableMigration < Cassmap::Migration
+
+        def self.up
+            execute <<CQL
+            CREATE TABLE trades_by_price (
+            id timeuuid,
+            price decimal,
+            quantity int,
+            symbol text,
+            PRIMARY KEY(price));
+    CQL
+        end
+
+        def self.down
+            execute "drop trades_by_price"
+        end
+    end
+
+after you've defined your schema files the typical Rake db commands work fine, just with cass as the parameter.
+
+    rake cass:create # creates database for environment based on cassmap.yml
+    rake cass:setup
+    rake cass:seed
+    rake cass:drop
+    rake cass:migrate
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'cassmap'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install cassmap
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/cassmap.gemspec

@@ -0,0 +1,34 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'cassmap/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "cassmap"
+  spec.version       = Cassmap::VERSION
+  spec.authors       = ["Ryan Svihla"]
+  spec.email         = ["rs@foundev.pro"]
+  spec.description   = %q{Cassandra ActiveModel implementation for Rails with migrations and full query table support.}
+  spec.summary       = <<SUMMARY
+  Good Cassandra data modeling embraces the distributed nature of the database, and makes heavy use of materialized views or as I like to refer to them "Query Tables". In this concept you denormalize your data and model your tables after the queries you need to preform in your application. Denormalization of course has downsides when it comes to data consistency and performance if you're making roundtrips for each table. Cassandra's api helps us solve the data consistency between query tables problem with the BATCH statment. Other Active Record implmentations do not allow you to batch these updates easily and most people resort to hand CQL and respositories to keep their data consisten. I aim to eliminate this boilerplate.
+SUMMARY
+  spec.homepage      = "https://github.com/rssvihla/cassmap"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files`.split($/)
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  spec.require_paths = ["lib"]
+  spec.has_rdoc = true
+  spec.extra_rdoc_files = 'README.md'
+
+  spec.required_ruby_version = ">= 2.0"
+  spec.add_runtime_dependency "cql-rb", "~> 1.2"
+  spec.add_runtime_dependency "activemodel", ">= 4.0.0"
+  spec.add_development_dependency "bundler", "~> 1.3"
+  spec.add_development_dependency "rake"
+  spec.add_development_dependency "rspec", "~> 2.1"
+
+  spec.requirements << 'Cassandra >= 2.0.0'
+
+end

data/lib/cassmap.rb

@@ -0,0 +1,5 @@
+require "cassmap/version"
+
+module Cassmap
+  # Your code goes here...
+end

data/lib/cassmap/version.rb

@@ -0,0 +1,3 @@
+module Cassmap
+  VERSION = "0.0.1"
+end

metadata

@@ -0,0 +1,133 @@
+--- !ruby/object:Gem::Specification
+name: cassmap
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Ryan Svihla
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2014-03-19 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: cql-rb
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.2'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.2'
+- !ruby/object:Gem::Dependency
+  name: activemodel
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: 4.0.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: 4.0.0
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.3'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.3'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '2.1'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '2.1'
+description: Cassandra ActiveModel implementation for Rails with migrations and full
+  query table support.
+email:
+- rs@foundev.pro
+executables: []
+extensions: []
+extra_rdoc_files:
+- README.md
+files:
+- .gitignore
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- cassmap.gemspec
+- lib/cassmap.rb
+- lib/cassmap/version.rb
+homepage: https://github.com/rssvihla/cassmap
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - '>='
+    - !ruby/object:Gem::Version
+      version: '2.0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements:
+- Cassandra >= 2.0.0
+rubyforge_project: 
+rubygems_version: 2.0.14
+signing_key: 
+specification_version: 4
+summary: Good Cassandra data modeling embraces the distributed nature of the database,
+  and makes heavy use of materialized views or as I like to refer to them "Query Tables".
+  In this concept you denormalize your data and model your tables after the queries
+  you need to preform in your application. Denormalization of course has downsides
+  when it comes to data consistency and performance if you're making roundtrips for
+  each table. Cassandra's api helps us solve the data consistency between query tables
+  problem with the BATCH statment. Other Active Record implmentations do not allow
+  you to batch these updates easily and most people resort to hand CQL and respositories
+  to keep their data consisten. I aim to eliminate this boilerplate.
+test_files: []