Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Evite un contre sens sur le stockage des données
  • Loading branch information
Filirom1 committed Aug 29, 2012
commit d51a1b616f661a55515dd362dca3dcc8840feef9
3 changes: 1 addition & 2 deletions _posts/2012-08-21-au-coeur-d-elasticsearch.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -101,8 +101,7 @@ Il faut donc interroger les deux bases : l'index inversé puis la base clé-vale
Get from index: "engine" => {Doc1,Doc2}
Get from storage: Doc1 AND Doc2 => ["Road to a Distributed Search Engine", "ElasticSearch a distributed, RESTful Search Engine"]


Mais le fait de stocker le document en plus de l'index est couteux en mémoire. Nous pouvons donc imaginer fonctionner sans stockage de documents : [ElasticSearch-source-field](http://www.elasticsearch.org/guide/reference/mapping/source-field.html), [Lucene-store-field](http://lucene.apache.org/core/3_6_0/api/all/org/apache/lucene/document/Field.Store.html)
Par défaut ElasticSearch [index et stocke](http://www.elasticsearch.org/guide/reference/mapping/source-field.html) la donnée de manière completement transparente pour l'utilisateur, mais ceci est [configurable](https://groups.google.com/d/msg/elasticsearch/k_YgO8xspXE/eqY_SHEwgCMJ).


## Requêtes et Analysers
Expand Down