bigbroda 0.0.6 → 0.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5b55ffa159ded2930f2f05fb0ba9bec08349d67e
-  data.tar.gz: fadc8c338d73773696b33e22c290a9048f155e00
+  metadata.gz: ee5bfec85d610513c98a0859842ce00827fc6447
+  data.tar.gz: 5ac1a4183d960946834461d5baa585b4510e1e1e
 SHA512:
-  metadata.gz: f2cea4afe0400929446ecfcb2d52964454af7a15a3d8b02ee42d54c885c2bd077008c6dd1a07edf3c1e9c696c9067df52ce86edfb85f59182cf9e34eb2a26b4e
-  data.tar.gz: 3069cc6deaa339ad86f4dd21c869312814c33754f889fd616207b8d2f92e98309d5ee2f73aa8dc42fb3f2cc0e5efa6f25d5f239c8b32bcfcc5866c482fedd7ab
+  metadata.gz: 930b75e37fd5402f3468651d2d2f3574ee82675fd952290c8a6bc613df221c60eae84c69361d1a5ff216a1f8d333545c5aea35f5e2cd377ff6acd5dde55090dc
+  data.tar.gz: bda1e4134eac5eeb36be1ed4ed9e7b47a0e9d2384ee3bcaf8b3778afe7bd1ec02485215fc36d7c4abb579f83913989e200f935ff429571b6f6369d4366812fb4

data/README.md

@@ -6,9 +6,9 @@ GoogleBigQuery ActiveRecord Adapter & standalone API client
 
 https://developers.google.com/bigquery/what-is-bigquery
 
-BigQuery is fantastic for running ad hoc aggregate queries across a very very large dataset - large web logs, ad analysis, sensor data, sales data... etc. Basically, many kinds of "full table scan" queries. Queries are written in a SQL-style language (you don't have to write custom MapReduce functions). 
+BigQuery is fantastic for running ad hoc aggregate queries across a very very large dataset - large web logs, ad analysis, sensor data, sales data... etc. Basically, many kinds of "full table scan" queries. Queries are written in a SQL-style language (you don't have to write custom MapReduce functions).
 
-But!, Bigquery has a constraint to consider before diving in, 
+But!, Bigquery has a constraint to consider before diving in,
 BQ is append only , that means that you can't update records or delete them.
 
 So, use BigQuery as an OLAP (Online Analytical Processing) service, not as OLTP (Online Transactional Processing). In other words, use BigQuery as a DataWareHouse.
@@ -21,6 +21,8 @@ Add 'google_bigquery' to your application's Gemfile or install it yourself as:
 
 ## Rails / ActiveRecord:
 
+This gem supports ActiveRecord >= 4
+
 #### Configure GoogleBigQuery:
 
     rails g google_bigquery:install
@@ -47,7 +49,7 @@ ActiveRecord connection in plain ruby:
 
 ```ruby
 ActiveRecord::Base.establish_connection(
-  :adapter => 'bigquery', 
+  :adapter => 'bigquery',
   :project => "MyBigQueryProject",
   :database => "MyBigTable"
 )
@@ -83,7 +85,7 @@ Then you will have to execute the migration programaticly. like this:
 ```ruby
 UserMigration.up
 ```
-or 
+or
 
 ```ruby
 AddPublishedToUser.change
@@ -133,7 +135,7 @@ User.create([{name: "miki"}, {name: "jara"}])
 
 ```
 
-NOTE: by default the adapter will set Id values as an SecureRandom.hex, and for now all the foreign keys are created as a STRING type 
+NOTE: by default the adapter will set Id values as an SecureRandom.hex, and for now all the foreign keys are created as a STRING type
 
 #### Deletion and edition of single rows:
 
@@ -156,10 +158,10 @@ User.bigquery_export(destination)
 ```
 where destination should be a valid google cloud store uri. The adapter will manage that , so you only need to pass the file name. Example:
 
-    User.bigquery_export("file.json") 
+    User.bigquery_export("file.json")
 
 the adapter will convert that option to gs://[configured_database]/[file.json]. Just be sure to create the bucket propperly in Cloud Storage panel.
-Also if you don't pass the file argument you will get an generated uri like: gs://[configured_database]/[table_name].json. 
+Also if you don't pass the file argument you will get an generated uri like: gs://[configured_database]/[table_name].json.
 
 #### Import
 
@@ -172,12 +174,12 @@ User.bigquery_import([an_array_with_paths_to_gs_uris])
 ```
 
 From multipart/related post:
-      
+
     PENDING
 
 ### Migrations:
 
-This adapter has migration support migrations built in, but 
+This adapter has migration support migrations built in, but
 
 ```ruby
 class CreateUsers < ActiveRecord::Migration
@@ -204,8 +206,8 @@ end
 
 ```
 
-Note: 
-+ Big query does not provide a way to update columns nor delete, so update_column, or remove_column migration are cancelled with an catched exception. 
+Note:
++ Big query does not provide a way to update columns nor delete, so update_column, or remove_column migration are cancelled with an catched exception.
 + Also the schema_migrations table is not created in DB, is created as a json file in db/schema_migrations.json instead. Be sure to add the file in your version control.
 
 ## Standalone Client:
@@ -278,13 +280,13 @@ GoogleBigquery::Dataset.list(@project_id)
 
 #### Create/Insert:
 
-```ruby  
+```ruby
 GoogleBigquery::Dataset.create(@project, {"datasetReference"=> { "datasetId" => @dataset_id }} )
 ```
 
 #### Delete:
 
-```ruby  
+```ruby
 GoogleBigquery::Dataset.delete(@project, @dataset_id }} )
 ```
 
@@ -292,10 +294,10 @@ GoogleBigquery::Dataset.delete(@project, @dataset_id }} )
 
   Updates information in an existing dataset. The update method replaces the entire dataset resource, whereas the patch method only replaces fields that are provided in the submitted dataset resource.
 
-```ruby  
+```ruby
 GoogleBigquery::Dataset.update(@project, @dataset_id,
       {"datasetReference"=> {
-       "datasetId" =>@dataset_id }, 
+       "datasetId" =>@dataset_id },
       "description"=> "foobar"} )
 ```
 
@@ -305,7 +307,7 @@ GoogleBigquery::Dataset.update(@project, @dataset_id,
 ```ruby
 GoogleBigquery::Dataset.patch(@project, @dataset_id,
         {"datasetReference"=> {
-         "datasetId" =>@dataset_id }, 
+         "datasetId" =>@dataset_id },
         "description"=> "foobar"} )
 ```
 
@@ -320,8 +322,8 @@ GoogleBigquery::Dataset.patch(@project, @dataset_id,
 @table_body = {  "tableReference"=> {
                     "projectId"=> @project,
                     "datasetId"=> @dataset_id,
-                    "tableId"=> @table_name}, 
-        "schema"=> [fields: 
+                    "tableId"=> @table_name},
+        "schema"=> [fields:
                       {:name=> "name", :type=> "string", :mode => "REQUIRED"},
                       {:name=>  "age", :type=> "integer"},
                       {:name=> "weight", :type=> "float"},
@@ -330,17 +332,17 @@ GoogleBigquery::Dataset.patch(@project, @dataset_id,
       }
 
 GoogleBigquery::Table.create(@project, @dataset_id, @table_body
-```   
+```
 
 #### Update:
 
 ```ruby
     GoogleBigquery::Table.update(@project, @dataset_id, @table_name,
         {"tableReference"=> {
-         "projectId" => @project, "datasetId" =>@dataset_id, "tableId"  => @table_name }, 
+         "projectId" => @project, "datasetId" =>@dataset_id, "tableId"  => @table_name },
         "description"=> "foobar"} )
 ```
-       
+
 #### Delete:
 
 ```ruby
@@ -354,7 +356,7 @@ GoogleBigquery::Table.delete(@project, @dataset_id, @table_name )
 ```
 
 ### Table Data
-  
+
   https://developers.google.com/bigquery/docs/reference/v2/tabledata
 
 #### InsertAll
@@ -406,7 +408,7 @@ GoogleBigquery::TableData.list(@project, @dataset_id, @table_name)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request
 
- 
+
 #TODO:
 
 ActiveRecord:

data/lib/google_bigquery/auth.rb

@@ -11,7 +11,7 @@ module GoogleBigquery
     end
 
     def authorize
-      @client = Google::APIClient.new
+      @client = Google::APIClient.new(application_name: "BigBroda", application_version: GoogleBigquery::VERSION )
       @client.authorization = @asserter.authorize
       @client.retries = @config.retries.to_i if @config.retries.to_i > 1
       @api = @client.discovered_api('bigquery', 'v2')

data/lib/google_bigquery/version.rb

@@ -1,3 +1,3 @@
 module GoogleBigquery
-  VERSION = "0.0.6"
+  VERSION = "0.0.7"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bigbroda
 version: !ruby/object:Gem::Version
-  version: 0.0.6
+  version: 0.0.7
 platform: ruby
 authors:
 - miguel michelson