searchkick 1.3.5 → 1.3.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e69261f029a233983def6aaec3cd101621807fe8
-  data.tar.gz: 93d6d5e53193af4ae04537c012845d336a9b7197
+  metadata.gz: 2665e44b0bd2b8e4bcceb5d9963acb49505914bb
+  data.tar.gz: f44ddcee8dd2b1ff0607aac73243a36a458179c5
 SHA512:
-  metadata.gz: 2a2f79b352af2ae191c719480e648e07fc8083e3d6c836632e5f1f5245786386bad8e0397d15f3c13771a7197e92052a9c2ba269de23f3f5858fb528642eff26
-  data.tar.gz: 57972ac3b439dcbf77bef6d9f121383f93822ae3e3c0b6bbf64baedbe0f46a2dd1dd8c9ded33a0384bb80abb5922a33bd216cdeea9271c25f7dc754fd0f7c5a4
+  metadata.gz: ea59d44e55010236af8b16a1c3b1d7e7f160081f137cbdd44e298d291c6ae84a966be25a405f21f970885f07c73bf6e76c6e56edf29cba234c2ba308b6ba5241
+  data.tar.gz: 28c80bb3061751507605bebf0a4dacb541a4f8cfd6b98156c3cbfad2aa9de03c916aa12715bc47769a3a79b154d82f4c2bc901d34a7d314e57f2ac0d96fe5ee4

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 1.3.6
+
+- Fixed `Job adapter not found` error
+
 ## 1.3.5
 
 - Added support for Elasticsearch 5.0 beta

data/README.md

@@ -2,7 +2,7 @@
 
 :rocket: Intelligent search made easy
 
-Searchkick learns what **your users** are looking for.  As more people search, it gets smarter and the results get better.  It’s friendly for developers - and magical for your users.
+Searchkick learns what **your users** are looking for. As more people search, it gets smarter and the results get better. It’s friendly for developers - and magical for your users.
 
 Searchkick handles:
 
@@ -265,7 +265,7 @@ User.search "fresh honey", match: :phrase
 
 ### Language
 
-Searchkick defaults to English for stemming.  To change this, use:
+Searchkick defaults to English for stemming. To change this, use:
 
 ```ruby
 class Product < ActiveRecord::Base
@@ -366,7 +366,7 @@ class Product < ActiveRecord::Base
 end
 ```
 
-Searchkick uses `find_in_batches` to import documents.  To eager load associations, use the `search_import` scope.
+Searchkick uses `find_in_batches` to import documents. To eager load associations, use the `search_import` scope.
 
 ```ruby
 class Product < ActiveRecord::Base
@@ -374,10 +374,12 @@ class Product < ActiveRecord::Base
 end
 ```
 
-By default, all records are indexed.  To control which records are indexed, use the `should_index?` method.
+By default, all records are indexed. To control which records are indexed, use the `should_index?` method together with the `search_import` scope.
 
 ```ruby
 class Product < ActiveRecord::Base
+  scope :search_import, -> { where(active: true) }
+
   def should_index?
     active # only index active records
   end
@@ -450,7 +452,7 @@ end
 
 #### Associations
 
-Data is **not** automatically synced when an association is updated.  If this is desired, add a callback to reindex:
+Data is **not** automatically synced when an association is updated. If this is desired, add a callback to reindex:
 
 ```ruby
 class Image < ActiveRecord::Base
@@ -478,11 +480,11 @@ Product.search "apple", track: {user_id: current_user.id}
 
 ### Keep Getting Better
 
-Searchkick can use conversion data to learn what users are looking for.  If a user searches for “ice cream” and adds Ben & Jerry’s Chunky Monkey to the cart (our conversion metric at Instacart), that item gets a little more weight for similar searches.
+Searchkick can use conversion data to learn what users are looking for. If a user searches for “ice cream” and adds Ben & Jerry’s Chunky Monkey to the cart (our conversion metric at Instacart), that item gets a little more weight for similar searches.
 
-The first step is to define your conversion metric and start tracking conversions.  The database works well for low volume, but feel free to use Redis or another datastore.
+The first step is to define your conversion metric and start tracking conversions. The database works well for low volume, but feel free to use Redis or another datastore.
 
-You do **not** need to clean up the search queries.  Searchkick automatically treats `apple` and `APPLES` the same.
+You do **not** need to clean up the search queries. Searchkick automatically treats `apple` and `APPLES` the same.
 
 Next, add conversions to the index.
 
@@ -510,7 +512,7 @@ rake searchkick:reindex CLASS=Product
 
 ### Personalized Results
 
-Order results differently for each user.  For example, show a user’s previously purchased products before other results.
+Order results differently for each user. For example, show a user’s previously purchased products before other results.
 
 ```ruby
 class Product < ActiveRecord::Base
@@ -537,7 +539,7 @@ Autocomplete predicts what a user will type, making the search experience faster
 
 **Note:** If you only have a few thousand records, don’t use Searchkick for autocomplete. It’s *much* faster to load all records into JavaScript and autocomplete there (eliminates network requests).
 
-First, specify which fields use this feature.  This is necessary since autocomplete can increase the index size significantly, but don’t worry - this gives you blazing faster queries.
+First, specify which fields use this feature. This is necessary since autocomplete can increase the index size significantly, but don’t worry - this gives you blazing faster queries.
 
 ```ruby
 class Book < ActiveRecord::Base
@@ -949,7 +951,7 @@ See the [complete list of analyzers](lib/searchkick/index.rb#L209).
 
 ## Deployment
 
-Searchkick uses `ENV["ELASTICSEARCH_URL"]` for the Elasticsearch server.  This defaults to `http://localhost:9200`.
+Searchkick uses `ENV["ELASTICSEARCH_URL"]` for the Elasticsearch server. This defaults to `http://localhost:9200`.
 
 ### Heroku
 
@@ -1376,7 +1378,7 @@ Product.search "ah", misspellings: {prefix_length: 2} # ah, no aha
 
 ## Large Data Sets
 
-For large data sets, check out [Keeping Elasticsearch in Sync](https://www.elastic.co/blog/found-keeping-elasticsearch-in-sync).  Searchkick will make this easy in the future.
+For large data sets, check out [Keeping Elasticsearch in Sync](https://www.elastic.co/blog/found-keeping-elasticsearch-in-sync). Searchkick will make this easy in the future.
 
 ## Testing
 
@@ -1476,7 +1478,7 @@ Before `0.3.0`, locations were indexed incorrectly. When upgrading, be sure to r
 
 ### Inconsistent Scores
 
-Due to the distributed nature of Elasticsearch, you can get incorrect results when the number of documents in the index is low.  You can [read more about it here](https://www.elastic.co/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch).  To fix this, do:
+Due to the distributed nature of Elasticsearch, you can get incorrect results when the number of documents in the index is low. You can [read more about it here](https://www.elastic.co/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch). To fix this, do:
 
 ```ruby
 class Product < ActiveRecord::Base

data/lib/searchkick/version.rb

@@ -1,3 +1,3 @@
 module Searchkick
-  VERSION = "1.3.5"
+  VERSION = "1.3.6"
 end

data/lib/searchkick.rb

@@ -12,6 +12,14 @@ require "searchkick/tasks"
 require "searchkick/middleware"
 require "searchkick/logging" if defined?(ActiveSupport::Notifications)
 
+# background jobs
+begin
+  require "active_job"
+rescue LoadError
+  # do nothing
+end
+require "searchkick/reindex_v2_job" if defined?(ActiveJob)
+
 module Searchkick
   class Error < StandardError; end
   class MissingIndexError < Error; end
@@ -152,13 +160,6 @@ module Searchkick
   end
 end
 
-ActiveSupport.on_load(:active_job) do
-  require "searchkick/reindex_v2_job"
-end
-
 # TODO find better ActiveModel hook
 ActiveModel::Callbacks.send(:include, Searchkick::Model)
-
-ActiveSupport.on_load(:active_record) do
-  ActiveRecord::Base.send(:extend, Searchkick::Model)
-end
+ActiveRecord::Base.send(:extend, Searchkick::Model) if defined?(ActiveRecord)

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: searchkick
 version: !ruby/object:Gem::Version
-  version: 1.3.5
+  version: 1.3.6
 platform: ruby
 authors:
 - Andrew Kane
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-09-28 00:00:00.000000000 Z
+date: 2016-10-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activemodel