algoliasearch 1.9.0 → 1.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1035690a7833a5235345419a3376a771932d281e
-  data.tar.gz: d7eb3c02b159845109c25b7e49b61191e72a2d2d
+  metadata.gz: 9aa3ec8a147ae10740f99b9f04eb82cd49b8731b
+  data.tar.gz: 9fe92762186104bb95e67f43be839694bfe40cb4
 SHA512:
-  metadata.gz: 57f1c99c147f759f6c6a70ecae88b30ec607ab886d720fcc426bf47b1a528028494b54d2edbfd40eb2e560074866b6453fd5727e117ecb9e26abe98ec14f91b3
-  data.tar.gz: b19a6880521c58d9fd74a4b62244b61aeb348b7f61c06aaf6d90e0565681c4daf2cb5f16d4fa8bcec60a3c2d9762b0d521ac12e742715f7028d56b2589b942f0
+  metadata.gz: 1ab1dae58906b5d01180379396e3ee00cd1c67a755a0ebfd29945f80c10a5813dfc8ccf431e0a6145e6a04108efc613f9aa2b9a0297ed1a6cede28d6de030262
+  data.tar.gz: f95d7a77dc2a6bc342985171f5de609c74ea3590a31cb12ab61be817b3d8c781fc5e9721f2540783ebbe1cdad3d82ed5c35538ce7d1a4ebf5810cd956aa0923b

data/ChangeLog

@@ -1,5 +1,8 @@
 CHANGELOG
 
+2016-07-11 1.10.0
+      * `{get,set}_settings` now take optional custom query parameters
+
 2016-06-17 1.9.0
       * New synonyms API
 

data/README.md

@@ -554,7 +554,65 @@ You can use the following optional arguments:
         </div>
       </td>
       <td class='client-readme-param-content'>
-        <p>Remove the stop words from query before executing it. Defaults to false. Contains a list of stop words from 41 languages (Arabic, Armenian, Basque, Bengali, Brazilian, Bulgarian, Catalan, Chinese, Czech, Danish, Dutch, English, Finnish, French, Galician, German, Greek, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Korean, Kurdish, Latvian, Lithuanian, Marathi, Norwegian, Persian, Polish, Portugese, Romanian, Russian, Slovak, Spanish, Swedish, Thai, Turkish, Ukranian, Urdu). In most use-cases, we don&#39;t recommend enabling this option.</p>
+        <p>Remove stop words from the query <strong>before</strong> executing it. Defaults to <code>false</code>. Use a boolean to enable/disable all 41 supported languages and a comma separated list of iso codes of the languages you want to use consider to enable the stopwords removal on a subset of them (select the one you have in your records). In most use-cases, you shouldn&#39;t need to enable this option.</p>
+
+<p>List of 41 supported languages with their associated iso code: Arabic=ar, Armenian=hy, Basque=eu, Bengali=bn, Brazilian=pt-br, Bulgarian=bg, Catalan=ca, Chinese=zh, Czech=cs, Danish=da, Dutch=nl, English=en, Finnish=fi, French=fr, Galician=gl, German=de, Greek=el, Hindi=hi, Hungarian=hu, Indonesian=id, Irish=ga, Italian=it, Japanese=ja, Korean=ko, Kurdish=ku, Latvian=lv, Lithuanian=lt, Marathi=mr, Norwegian=no, Persian (Farsi)=fa, Polish=pl, Portugese=pt, Romanian=ro, Russian=ru, Slovak=sk, Spanish=es, Swedish=sv, Thai=th, Turkish=tr, Ukranian=uk, Urdu=ur</p>
+
+<p>Stop words removal is applied on query words that are not interpreted as a prefix. The behavior depends of the queryType parameter:</p>
+
+<ul>
+<li><p><code>queryType=prefixLast</code> means the last query word is a prefix and it won’t be considered for stop words removal</p></li>
+<li><p><code>queryType=prefixNone</code> means no query word are prefix, stop words removal will be applied on all query words</p></li>
+<li><p><code>queryType=prefixAll</code> means all query terms are prefix, stop words won’t be removed</p></li>
+</ul>
+
+<p>This parameter is useful when you have a query in natural language like “what is a record?”. In this case, before executing the query, we will remove “what”, “is” and “a” in order to just search for “record”. This removal will remove false positive because of stop words, especially when combined with optional words. For most use cases, it is better to not use this feature as people search by keywords on search engines.</p>
+
+      </td>
+    </tr>
+    
+
+  
+    <tr>
+      <td valign='top'>
+        <div class='client-readme-param-container'>
+          <div class='client-readme-param-container-inner'>
+            <div class='client-readme-param-name'><code>exactOnSingleWordQuery</code></div>
+            <div class="client-readme-param-meta"><div><em>Default: <strong>attribute</strong></em></div></div>
+          </div>
+        </div>
+      </td>
+      <td class='client-readme-param-content'>
+        <p>This parameter control how the <code>exact</code> ranking criterion is computed when the query contains one word. There is three different values:</p>
+
+<ul>
+<li><p><code>none</code>: no exact on single word query</p></li>
+<li><p><code>word</code>: exact set to 1 if the query word is found in the record. The query word needs to have at least 3 chars and not be part of our stop words dictionary</p></li>
+<li><p><code>attribute</code> (default): exact set to 1 if there is an attribute containing a string equals to the query</p></li>
+</ul>
+
+      </td>
+    </tr>
+    
+
+  
+    <tr>
+      <td valign='top'>
+        <div class='client-readme-param-container'>
+          <div class='client-readme-param-container-inner'>
+            <div class='client-readme-param-name'><code>alternativesAsExact</code></div>
+            <div class="client-readme-param-meta"><div><em>Default: <strong>["ignorePlurals", "singleWordSynonym"]</strong></em></div></div>
+          </div>
+        </div>
+      </td>
+      <td class='client-readme-param-content'>
+        <p>Specify the list of approximation that should be considered as an exact match in the ranking formula:</p>
+
+<ul>
+<li><p><code>ignorePlurals</code>: alternative words added by the ignorePlurals feature</p></li>
+<li><p><code>singleWordSynonym</code>: single-word synonym (For example &quot;NY&quot; = &quot;NYC&quot;)</p></li>
+<li><p><code>multiWordsSynonym</code>: multiple-words synonym (For example &quot;NY&quot; = &quot;New York&quot;)</p></li>
+</ul>
 
       </td>
     </tr>
@@ -817,7 +875,7 @@ You can use the following optional arguments:
         </div>
       </td>
       <td class='client-readme-param-content'>
-        <p>A string that contains the list of attributes you want to highlight according to the query. Attributes are separated by commas. You can also use a string array encoding (for example <code>[&quot;name&quot;,&quot;address&quot;]</code>). If an attribute has no match for the query, the raw value is returned. By default, all indexed attributes are highlighted. You can use <code>*</code> if you want to highlight all attributes. A matchLevel is returned for each highlighted attribute and can contain:</p>
+        <p>A string that contains the list of attributes you want to highlight according to the query. Attributes are separated by commas. You can also use a string array encoding (for example <code>[&quot;name&quot;,&quot;address&quot;]</code>). If an attribute has no match for the query, the raw value is returned. By default, all indexed attributes are highlighted (as long as they are strings). You can use <code>*</code> if you want to highlight all attributes. A matchLevel is returned for each highlighted attribute and can contain:</p>
 
 <ul>
 <li><strong>full</strong>: If all the query terms were found in the attribute.</li>
@@ -1183,6 +1241,13 @@ puts settings.to_json
 index.set_settings({"customRanking" => ["desc(followers)"]})
 ```
 
+## Slave settings
+
+You can forward all settings updates to the slaves of an index by using the `forwardToSlaves` option:
+
+```ruby
+index.set_settings({"customRanking" => ["desc(followers)"]}, {"forwardToSlave" => true})
+```
 
 ## Indexing parameters
 
@@ -1812,12 +1877,68 @@ To get a full description of how the Ranking works, you can have a look at our <
         <div class='client-readme-param-container'>
           <div class='client-readme-param-container-inner'>
             <div class='client-readme-param-name'><code>removeStopWords</code></div>
-            <div class="client-readme-param-meta"><div><em>Type: <strong>boolean</strong></em></div><div><em>Default: <strong>false</strong></em></div></div>
+            <div class="client-readme-param-meta"><div><em>Type: <strong>boolean or string array</strong></em></div><div><em>Default: <strong>false</strong></em></div></div>
           </div>
         </div>
       </td>
       <td class='client-readme-param-content'>
-        <p>Remove stop words from query before executing it. Defaults to false. Contains stop words for 41 languages (Arabic, Armenian, Basque, Bengali, Brazilian, Bulgarian, Catalan, Chinese, Czech, Danish, Dutch, English, Finnish, French, Galician, German, Greek, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Korean, Kurdish, Latvian, Lithuanian, Marathi, Norwegian, Persian, Polish, Portugese, Romanian, Russian, Slovak, Spanish, Swedish, Thai, Turkish, Ukranian, Urdu)</p>
+        <p>Remove stop words from the query <strong>before</strong> executing it. Defaults to <code>false</code>. Use a boolean to enable/disable all 41 supported languages and an array of string listing the iso codes of the languages you want to use consider to enable the stop words removal on a subset of them (select the one you have in your records).</p>
+
+<p>List of 41 supported languages with their associated iso code: Arabic=ar, Armenian=hy, Basque=eu, Bengali=bn, Brazilian=pt-br, Bulgarian=bg, Catalan=ca, Chinese=zh, Czech=cs, Danish=da, Dutch=nl, English=en, Finnish=fi, French=fr, Galician=gl, German=de, Greek=el, Hindi=hi, Hungarian=hu, Indonesian=id, Irish=ga, Italian=it, Japanese=ja, Korean=ko, Kurdish=ku, Latvian=lv, Lithuanian=lt, Marathi=mr, Norwegian=no, Persian (Farsi)=fa, Polish=pl, Portugese=pt, Romanian=ro, Russian=ru, Slovak=sk, Spanish=es, Swedish=sv, Thai=th, Turkish=tr, Ukranian=uk, Urdu=ur.</p>
+
+<p>Stop words removal is applied on query words that are not interpreted as a prefix. The behavior depends of the queryType setting:</p>
+
+<ul>
+<li><p><code>queryType=prefixLast</code> means the last query word is a prefix and it won’t be considered for stop words removal</p></li>
+<li><p><code>queryType=prefixNone</code> means no query word are prefix, stop words removal will be applied on all query words</p></li>
+<li><p><code>queryType=prefixAll</code> means all query terms are prefix, stop words won’t be removed</p></li>
+</ul>
+
+<p>This index setting is useful when you have queries in natural language like “what is a record?”. In this case, before executing the query, we will remove “what”, “is” and “a” in order to just search for “record”. This removal will remove false positive because of stop words. For most use cases, it is better to not use this feature as people search by keywords on search engines.</p>
+
+      </td>
+    </tr>
+    
+  
+    <tr>
+      <td valign='top'>
+        <div class='client-readme-param-container'>
+          <div class='client-readme-param-container-inner'>
+            <div class='client-readme-param-name'><code>exactOnSingleWordQuery</code></div>
+            <div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div><div><em>Default: <strong>attribute</strong></em></div></div>
+          </div>
+        </div>
+      </td>
+      <td class='client-readme-param-content'>
+        <p>This parameter controls how the <code>exact</code> ranking criterion is computed when the query contains one word. There is three different values:</p>
+
+<ul>
+<li><p><code>none</code>: no <code>exact</code> on single word query</p></li>
+<li><p><code>word</code>: <code>exact</code> set to 1 if the query word is found in the record. The query word needs to have at least 3 chars and not be part of our stop words dictionary</p></li>
+<li><p><code>attribute</code> (default): exact set to 1 if there is an attribute containing a string equals to the query</p></li>
+</ul>
+
+      </td>
+    </tr>
+    
+  
+    <tr>
+      <td valign='top'>
+        <div class='client-readme-param-container'>
+          <div class='client-readme-param-container-inner'>
+            <div class='client-readme-param-name'><code>alternativesAsExact</code></div>
+            <div class="client-readme-param-meta"><div><em>Type: <strong>string array</strong></em></div><div><em>Default: <strong>["ignorePlurals", "singleWordSynonym"]</strong></em></div></div>
+          </div>
+        </div>
+      </td>
+      <td class='client-readme-param-content'>
+        <p>Specify the list of approximation that should be considered as an exact match in the ranking formula:</p>
+
+<ul>
+<li><p><code>ignorePlurals</code>: alternative words added by the ignorePlurals feature</p></li>
+<li><p><code>singleWordSynonym</code>: single-word synonym (For example &quot;NY&quot; = &quot;NYC&quot;)</p></li>
+<li><p><code>multiWordsSynonym</code>: multiple-words synonym (For example &quot;NY&quot; = &quot;New York&quot;)</p></li>
+</ul>
 
       </td>
     </tr>

data/lib/algolia/index.rb

@@ -419,21 +419,22 @@ module Algolia
     #
     # Set settings for this index
     #
-    def set_settings(new_settings)
-      client.put(Protocol.settings_uri(name), new_settings.to_json)
+    def set_settings(new_settings, options = {})
+      client.put(Protocol.settings_uri(name, options), new_settings.to_json)
     end
 
     # Set settings for this index and wait end of indexing
     #
-    def set_settings!(new_settings)
-      res = set_settings(new_settings)
+    def set_settings!(new_settings, options = {})
+      res = set_settings(new_settings, options)
       wait_task(res["taskID"])
       return res
     end
 
     # Get settings of this index
-    def get_settings
-      client.get("#{Protocol.settings_uri(name)}?getVersion=2", :read)
+    def get_settings(options = {})
+      options['getVersion'] = 2 if !options[:getVersion] && !options['getVersion']
+      client.get("#{Protocol.settings_uri(name, options)}", :read)
     end
 
     # List all existing user keys with their associated ACLs

data/lib/algolia/protocol.rb

@@ -88,8 +88,9 @@ module Algolia
       "#{index_uri(index)}/#{CGI.escape(object_id)}/partial#{params}"
     end
 
-    def Protocol.settings_uri(index)
-      "#{index_uri(index)}/settings"
+    def Protocol.settings_uri(index, params = {})
+      params = params.nil? || params.size == 0 ? "" : "?#{to_query(params)}"
+      "#{index_uri(index)}/settings#{params}"
     end
 
     def Protocol.clear_uri(index)

data/lib/algolia/version.rb

@@ -1,3 +1,3 @@
 module Algolia
-  VERSION = "1.9.0"
+  VERSION = "1.10.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: algoliasearch
 version: !ruby/object:Gem::Version
-  version: 1.9.0
+  version: 1.10.0
 platform: ruby
 authors:
 - Algolia
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-06-17 00:00:00.000000000 Z
+date: 2016-07-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httpclient
@@ -131,7 +131,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.5.1
+rubygems_version: 2.4.8
 signing_key: 
 specification_version: 4
 summary: A simple Ruby client for the algolia.com REST API