must means: The clause (query) must appear in matching documents. These clauses must match, like logical AND. should means: At least one of these clauses must match, like logical OR. Basically they are used like logical operators AND and OR. See this. Now in a bool query: must means: Clauses that must match for the … Read more
OR is spelled should AND is spelled must NOR is spelled should_not Example: You want to see all the items that are (round AND (red OR blue)): { “query”: { “bool”: { “must”: [ { “term”: {“shape”: “round”} }, { “bool”: { “should”: [ {“term”: {“color”: “red”}}, {“term”: {“color”: “blue”}} ] } } ] } … Read more
This happens when Elasticsearch thinks the disk is running low on space so it puts itself into read-only mode. By default Elasticsearch’s decision is based on the percentage of disk space that’s free, so on big disks this can happen even if you have many gigabytes of free space. The flood stage watermark is 95% … Read more
For a concise list of all indices in your cluster, call curl http://localhost:9200/_aliases this will give you a list of indices and their aliases. If you want it pretty-printed, add pretty=true: curl http://localhost:9200/_aliases?pretty=true The result will look something like this, if your indices are called old_deuteronomy and mungojerrie: { “old_deuteronomy” : { “aliases” : { … Read more
I’ll try to explain with a real example since the answer and replies you got don’t seem to help you. When you download elasticsearch and start it up, you create an elasticsearch node which tries to join an existing cluster if available or creates a new one. Let’s say you created your own new cluster … Read more
As the creator of ElasticSearch, maybe I can give you some reasoning on why I went ahead and created it in the first place :). Using pure Lucene is challenging. There are many things that you need to take care for if you want it to really perform well, and also, its a library, so … Read more
If you ever need to delete all the indexes, this may come in handy: curl -X DELETE ‘http://localhost:9200/_all’ Powershell: Invoke-WebRequest -method DELETE http://localhost:9200/_all
Yep, Use a better option source filter. If you’re searching with JSON it’ll look something like this: { “_source”: [“user”, “message”, …], “query”: …, “size”: … } In ES 2.4 and earlier, you could also use the fields option to the search API: { “fields”: [“user”, “message”, …], “query”: …, “size”: … } This is … Read more
I think lucene syntax is supported so: http://localhost:9200/foo/_search?pretty=true&q=*:* size defaults to 10, so you may also need &size=BIGNUMBER to get more than 10 items. (where BIGNUMBER equals a number you believe is bigger than your dataset) BUT, elasticsearch documentation suggests for large result sets, using the scan search type. EG: curl -XGET ‘localhost:9200/foo/_search?search_type=scan&scroll=10m&size=50’ -d ‘ … Read more
Update Now that the question scope has been corrected, I might add something in this regard as well: There are many comparisons between Apache Solr and ElasticSearch available, so I’ll reference those I found most useful myself, i.e. covering the most important aspects: Bob Yoplait already linked kimchy’s answer to ElasticSearch, Sphinx, Lucene, Solr, Xapian. … Read more