Elasticsearch 0.90.2
See issues on GitHub
Release Notes
Breaking changes:
- Add a minimum_should_match parameter when Common query has only high frequent terms #3188
- Change Version methods to be more readable #3124
New features:
- Add @doc_as_upsert@ option to update api #3195
Enhancements:
- Add Arabic/PersianNormalizationFilters from Lucene #3231
- Add Lucene CommonGrams/CommonGramsQuery token fiter #3202
- Geohash enhancements for geopoints:
- Expose fielddata "fields" param in standard in indicesStatsRequest #3205
- Expose timeout in nodes_info REST API #3191
- Compress PagedBytesAtomicFieldData's termOrdToBytesOffset #3186
- Pack the ordinals in field data for single valued fields #3185
- custom_score could support a filter directly #3167
- Merge Settings are misleading #3166
- missing/exists filters should also work for objects #3141
- Update plugin manager #3112
- Can't define multiple predefined date formats using @||@ #2132
- Terms Filter Lookup:
Bug fixes:
- Deleting or closing an index doesn't clean the memory properly #3232
- ElasticSearch 0.90 fails when "highlight" contains a field of type "long" #3211
- "fielddata" qs param setting idCache, not fieldData #3204
- NPE in query execution of boolean filter in 0.90.1 #3177
- has_child & has_parent queries don't take deletes into account #3144
- FVH can result in massive CPU & RAM usage if MultPhraseQuery is large #3142
- FVH produces StringArrayIndexOutOfBounds if stored field is used #3140
- has_parent query returning no results with multi level child docs. #3139
- source exclusion mapping prevents geo shape coordinates to be returned in query result source field #2944
- Improved Debian package #2515
- Regresion: geo distance filter - filters out proper geohashes #3073
- Thread pool: rename @capacity@ to @queue_size@ #3161
- Fix offsets handling of the n-gram and edge n-gram tokenizers and token filters #3317