Add 7.0.0 Release Notes #41029
Merged
Add 7.0.0 Release Notes #41029
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
|
Pinging @elastic/es-docs |
lcawl
approved these changes
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
|
|
||
| Authentication:: | ||
| * Security: remove wrapping in put user response {pull}33512[#33512] (issue: {issue}32332[#32332]) | ||
| * Enhance Invalidate Token API {pull}35388[#35388] (issues: {issue}34556[#34556], {issue}35115[#35115]) |
There was a problem hiding this comment.
I think #35388 is not a breaking change. Rather, it should be under "enhancements"
lcawl
reviewed
Apr 9, 2019
| Authentication:: | ||
| * Security: remove wrapping in put user response {pull}33512[#33512] (issue: {issue}32332[#32332]) | ||
| * Enhance Invalidate Token API {pull}35388[#35388] (issues: {issue}34556[#34556], {issue}35115[#35115]) | ||
| * Remove bwc logic for token invalidation {pull}36893[#36893] (issue: {issue}36727[#36727]) |
There was a problem hiding this comment.
@jkakavas Should this be described in the Breaking changes documentation (https://www.elastic.co/guide/en/elasticsearch/reference/7.0/breaking-changes-7.0.html) ?
lcawl
reviewed
Apr 9, 2019
| Aggregations:: | ||
| * Remove support for deprecated params._agg/_aggs for scripted metric aggregations {pull}32979[#32979] (issues: {issue}29328[#29328], {issue}31597[#31597]) | ||
| * Percentile/Ranks should return null instead of NaN when empty {pull}30460[#30460] (issue: {issue}29066[#29066]) | ||
| * Render sum as zero if count is zero for stats aggregation {pull}27193[#27193] (issue: {issue}26893[#26893]) |
There was a problem hiding this comment.
I don't see documentation for #27193 in the Breaking Changes docs
lcawl
reviewed
Apr 9, 2019
| * Remove implicit index monitor privilege {pull}37774[#37774] | ||
|
|
||
| CCR:: | ||
| * Change get autofollow patterns API response format {pull}36203[#36203] (issue: {issue}36049[#36049]) |
There was a problem hiding this comment.
I think info about #36203 missing from the Breaking changes page too. Unless it's only a breaking change in 6.x?
lcawl
reviewed
Apr 9, 2019
|
|
||
| CCR:: | ||
| * Change get autofollow patterns API response format {pull}36203[#36203] (issue: {issue}36049[#36049]) | ||
| * Follow stats api should return a 404 when requesting stats for a non existing index {pull}37220[#37220] (issue: {issue}37021[#37021]) |
There was a problem hiding this comment.
Likewise, not sure if this is a valid breaking change in 6.7, 7.0 or neither: #37220
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
lcawl
reviewed
Apr 9, 2019
polyfractal
added a commit
that referenced
this pull request
Apr 10, 2019
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.
Phew! :)
Note: this is targeting
7.0branch