-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/master' into feature-ingest
- Loading branch information
Showing
460 changed files
with
7,215 additions
and
7,145 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
name: 8.0 Breaking change | ||
about: Breaking changes from 7.x -> 8.0 | ||
title: "[Breaking change]" | ||
labels: Team:Elasticsearch UI, Feature:Upgrade Assistant | ||
assignees: '' | ||
|
||
--- | ||
|
||
## Change description | ||
|
||
**Which release will ship the breaking change?** | ||
|
||
<!-- e.g., v7.6.2 --> | ||
|
||
**Describe the change. How will it manifest to users?** | ||
|
||
**What percentage of users will be affected?** | ||
|
||
<!-- e.g., Roughly 75% will need to make changes to x. --> | ||
|
||
**What can users to do to address the change manually?** | ||
|
||
<!-- If applicable, describe the manual workaround --> | ||
|
||
**How could we make migration easier with the Upgrade Assistant?** | ||
|
||
**Are there any edge cases?** | ||
|
||
## Test Data | ||
|
||
Provide test data. We can’t build a solution without data to test it against. | ||
|
||
## Cross links | ||
|
||
Cross-link to relevant [Elasticsearch breaking changes](https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-8.0.html). |
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
Oops, something went wrong.