Commit 54822e6f956bfd4309dd19b0fe93e49e035fb51d

Authored by Andrew Kane
1 parent d13f9e3b

Better explanation

Showing 1 changed file with 2 additions and 2 deletions   Show diff stats
README.md
... ... @@ -43,7 +43,7 @@ There is also a rake task.
43 43 rake searchkick:reindex CLASS=Book
44 44 ```
45 45  
46   -Thanks to Jaroslav Kalistsuk for the [original implementation](https://gist.github.com/jarosan/3124884), and Clinton Gormley for a [good post](http://www.elasticsearch.org/blog/changing-mapping-with-zero-downtime/) on this.
  46 +Thanks to Jaroslav Kalistsuk for the [original implementation](https://gist.github.com/jarosan/3124884) and Clinton Gormley for a [good post](http://www.elasticsearch.org/blog/changing-mapping-with-zero-downtime/) on this.
47 47  
48 48 ## Elasticsearch Gotchas
49 49  
... ... @@ -57,7 +57,7 @@ curl "http://localhost:9200/books/_mapping?pretty=1"
57 57  
58 58 ### Inconsistent Scores
59 59  
60   -Elasticsearch was built to be distributed. However, with a low number of documents, the default settings can give us incorrect results. You can [read more about it here](http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/). To fix this, set the search type to `dfs_query_and_fetch`. Alternatively, you can just use one shard with `settings: {number_of_shards: 1}`.
  60 +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](http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/). To fix this, set the search type to `dfs_query_and_fetch`. Alternatively, you can just use one shard with `settings: {number_of_shards: 1}`.
61 61  
62 62 ## Installation
63 63  
... ...