Feature/6.0 breaking changes #2944
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
…ord_len (a synonym for max_word_length) have been removed.
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.
…tion has been removed from the distance_type parameter.
…been removed. If provided, it will be ignored and issue a deprecation warning.
… removed. If provided, it will be ignored and issue a deprecation warning. The query_string query now splits on operator only.
…. If provided, it will be ignored and issue a deprecation warning. The tie_breaker parameter must be used instead.
… has been removed, use an explicit quoted query instead. If provided, it will be ignored and issue a deprecation warning.
…removed from simple_query_string.
…nstant_score_filter (synonyms for constant_score) have been removed.
…ch. The unified highlighter outputs the same highlighting when index_options is set to offsets.
…e.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.
…ing has been removed, the store stats do not report throttle_time anymore.
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.
Mpdreamz
approved these changes
Dec 12, 2017
There was a problem hiding this comment.
LGTM apart from some super pedantic comment.
I think its best not to try and merge the target branch on an open PR as with this commit but rather to rebase it in the future.
| ///<summary>A collection of filters to use for the analysis</summary> | ||
| public string[] Filter { get; set; } | ||
| /// <inheritdoc /> | ||
| public string[] Filter { get; set; } |
There was a problem hiding this comment.
| @@ -21,7 +21,7 @@ public enum RewriteMultiTerm | |||
| /// <summary> | |||
| /// A rewrite method that first translates each term into a should clause in a boolean query, and keeps the scores | |||
| /// as computed by the query. Note that typically such scores are meaningless to the user, and require non-trivial | |||
| /// CPU to compute, so it’s almost always better to use constant_score_auto. This rewrite method will hit too many | |||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First set of changes from #2923