term query matches a single term as it is : the value is not analyzed. So, it doesn’t have to be lowercased depending on what you have indexed. If you provided Bennett at index time and the value is not analyzed, the following query won’t return anything : { “query”: { “term” : { “user” … Read more
You can use REINDEX to do that. Reindex does not attempt to set up the destination index. It does not copy the settings of the source index. You should set up the destination index prior to running a _reindex action, including setting up mappings, shard counts, replicas, etc. First copy the index to a new … Read more
I’m using nGram, too. I use standard tokenizer and nGram just as a filter. Here is my setup: { “index”: { “index”: “my_idx”, “type”: “my_type”, “analysis”: { “index_analyzer”: { “my_index_analyzer”: { “type”: “custom”, “tokenizer”: “standard”, “filter”: [ “lowercase”, “mynGram” ] } }, “search_analyzer”: { “my_search_analyzer”: { “type”: “custom”, “tokenizer”: “standard”, “filter”: [ “standard”, “lowercase”, “mynGram” … Read more
You can use the terms aggregation. { “size”: 0, “aggs” : { “langs” : { “terms” : { “field” : “language”, “size” : 500 } } }} The size parameter within the aggregation specifies the maximum number of terms to include in the aggregation result. If you need all results, set this to a value … Read more
To fix this, add curl option -H ‘Content-Type: application/json’ This error is due to strict content-type checking introduced in ElasticSearch 6.0, as explained in this post Starting from Elasticsearch 6.0, all REST requests that include a body must also provide the correct content-type for that body.
Lucene is a Java library. You can include it in your project and refer to its functions using function calls. Elasticsearch is a JSON Based, Distributed, web server built over Lucene. Though it’s Lucene who is doing the actual work beneath, Elasticsearch provides us a convenient layer over Lucene. Each shard that gets created in … Read more
By default, Elasticsearch will re-assign shards to nodes dynamically. However, if you’ve disabled shard allocation (perhaps you did a rolling restart and forgot to re-enable it), you can re-enable shard allocation. # v0.90.x and earlier curl -XPUT ‘localhost:9200/_settings’ -d ‘{ “index.routing.allocation.disable_allocation”: false }’ # v1.0+ curl -XPUT ‘localhost:9200/_cluster/settings’ -d ‘{ “transient” : { “cluster.routing.allocation.enable” : … Read more
I believe if you combine the delete by query with a match all it should do what you are looking for, something like this (using your example): curl -XDELETE ‘http://localhost:9200/twitter/tweet/_query’ -d ‘{ “query” : { “match_all” : {} } }’ Or you could just delete the type: curl -XDELETE http://localhost:9200/twitter/tweet Note: XDELETE is deprecated for … Read more
Vivek’s answer sysctl -w vm.max_map_count=262144 is correct, however, the setting will only last for the duration of the session. If the host reboots, the setting will be reset to the original value. If you want to set this permanently, you need to edit /etc/sysctl.conf and set vm.max_map_count to 262144. When the host reboots, you can … Read more
The size param should be a param for the terms query example: curl -XPOST “http://localhost:9200/imoveis/_search?pretty=1” -d’ { “size”: 0, “aggregations”: { “bairro_count”: { “terms”: { “field”: “bairro.raw”, “size”: 10000 } } } }’ Use size: 0 for ES version 2 and prior. Setting size:0 is deprecated in 2.x onwards, due to memory issues inflicted on … Read more