You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Breaking Changes
Document API Changes
- version type force remove - Deleted enum value
- found field removed in the Delete API - Deleted property
Mapping Changes
- The include_in_all mapping parameter is now disallowed - Deleted all IncludeInAll and include_in_all references
* The deprecated min_word_len (a synonym for min_word_length) and max_word_len (a synonym for max_word_length) have been removed.
* Support custom normalizer in Analyze API
Analyze API can analyze normalizer and custom normalizer. In previous versions of Elasticsearch, Analyze API is requiring a tokenizer or analyzer parameter. In Elasticsearch 6.0.0, Analyze API can analyze a text as a keyword field with custom normalizer or if char_filter/filter is set and tokenizer/analyzer is not set.
* For geo_distance queries, sorting, and aggregations the sloppy_arc option has been removed from the distance_type parameter.
* The disable_coord parameter of the bool and common_terms queries has been removed. If provided, it will be ignored and issue a deprecation warning.
* The split_on_whitespace parameter for the query_string query has been removed. If provided, it will be ignored and issue a deprecation warning. The query_string query now splits on operator only.
* The use_dis_max parameter for the query_string query has been removed. If provided, it will be ignored and issue a deprecation warning. The tie_breaker parameter must be used instead.
* The auto_generate_phrase_queries parameter for the query_string query has been removed, use an explicit quoted query instead. If provided, it will be ignored and issue a deprecation warning.
* The all_fields parameter for the query_string has been removed. Also removed from simple_query_string.
* The deprecated multi term rewrite parameters constant_score_auto, constant_score_filter (synonyms for constant_score) have been removed.
* The postings highlighter has been removed from Lucene and Elasticsearch. The unified highlighter outputs the same highlighting when index_options is set to offsets.
* Store throttling has been removed. As a consequence, the indices.store.throttle.type and indices.store.throttle.max_bytes_per_sec cluster settings and the index.store.throttle.type and index.store.throttle.max_bytes_per_sec index settings are not recognized anymore.
* Removal of throttle_time in the store stats. Given that store throttling has been removed, the store stats do not report throttle_time anymore.
* FS stats no longer reports if the disk spins
Elasticsearch has defaulted to assuming that it is running on SSDs since the 2.x series of Elasticsearch. As such, Elasticsearch no longer needs to collect information from the operating system as to whether or not the underlying disks of each data path spin or not. While this functionality was no longer needed starting in the 2.x series of Elasticsearch, it was maintained in the filesystem section of the nodes stats APIs. This information has now been removed.
* Fix tests
Copy file name to clipboardExpand all lines: src/Nest/Mapping/TypeMapping.cs
-9Lines changed: 0 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,6 @@ public interface ITypeMapping
17
17
[JsonProperty("numeric_detection")]
18
18
bool?NumericDetection{get;set;}
19
19
20
-
[JsonProperty("include_in_all")]
21
-
bool?IncludeInAll{get;set;}
22
-
23
20
[Obsolete("Scheduled to be removed in 6.0. Default analyzers can no longer be specified at the type level. Use an index or field level analyzer instead.")]
24
21
[JsonProperty("analyzer")]
25
22
stringAnalyzer{get;set;}
@@ -70,8 +67,6 @@ public class TypeMapping : ITypeMapping
0 commit comments