If you’re ok with having all root fields except the nested one and then only the matching inner hits in the nested field, then we can re-use the previous answer like this by specifying a slightly more involved source filtering parameter: { “_source”: { “includes”: [ “*” ], “excludes”: [ “users” ] }, “query”: { … Read more
This is quite easy within Elasticsearch itself! Anytime you would specify an index, you can separate additional indices by comma. curl -XGET ‘http://localhost:9200/index1,index2/_search?q=yourQueryHere’ You can also search all indices with _all. curl -XGET ‘http://localhost:9200/_all/_search?q=yourQueryHere’ Here’s some helpful documentation from elasticsearch’s website. This site has TONS of info, but it is a bit difficult to find … Read more
If you like me have a lot of disk you can tune the watermark setting and use byte values instead of percentages: NB! Use either percentage values or byte values. You cannot mix the usage of percentage/ratio values and byte values within the watermark settings. Either all values are set to percentage/ratio values, or all … Read more
I had an orphaned Java process related to Elasticsearch. Killing it solved the lock issue. ps aux | grep ‘java’ kill -9 <PID>
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.
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
Nested documents are powerful because you retain certain attribute connections but there’s the downside of not being able to iterate over them as discussed here. With that being said you could flatten the users attributes using the copy_to feature like so: PUT my-index-000001 { “mappings”: { “properties”: { “user__first_flattened”: { “type”: “keyword” }, “user”: { … Read more
You’d need to use the field that is supposed to be unique as id for your documents. By default a new document with existing id would override the existing document with same id, but you can switch to op_type=create in order to get back an error if a document with same id already exists. There’s … Read more
The support for ActiveRecord associations in Tire is working, but requires couple of tweaks inside your application. There’s no question the library should do better job here, and in the future it certainly will. That said, here is a full-fledged example of Tire configuration to work with Rails’ associations in elasticsearch: active_record_associations.rb Let me highlight … Read more
Lucene uses a byte buffer internally that uses 32bit integers for addressing. By definition this limits the size of the documents. So 2GB is max in theory. In ElasticSearch: There is a max http request size in the ES GitHub code, and it is set against Integer.MAX_VALUE or 2^31-1. So, basically, 2GB is the maximum … Read more