mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 16:03:20 -04:00
d3853f4789
# Backport This will backport the following commits from `main` to `8.16`: - [[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)](https://github.com/elastic/kibana/pull/216693) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jesus Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-04T13:37:06Z","message":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/207096\n\nThis continues the work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES returns a 200 response containing an error field when we\nwait for the update mappings task. This case wasn't being handled. This\nPR handles that case, when we find a `search_phase_execution_exception`\nin the ES response we return a retryable error that sends us back to the\nupdate mappings state. It does it for both migration algorithms, the\npriority is ZDT but seemed like a nice to have in both.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"49380143432b654cf1b849d8c77b3abc2fb3aeb4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-major","backport:current-major","v9.1.0"],"title":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception","number":216693,"url":"https://github.com/elastic/kibana/pull/216693","mergeCommit":{"message":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/207096\n\nThis continues the work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES returns a 200 response containing an error field when we\nwait for the update mappings task. This case wasn't being handled. This\nPR handles that case, when we find a `search_phase_execution_exception`\nin the ES response we return a retryable error that sends us back to the\nupdate mappings state. It does it for both migration algorithms, the\npriority is ZDT but seemed like a nice to have in both.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"49380143432b654cf1b849d8c77b3abc2fb3aeb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216693","number":216693,"mergeCommit":{"message":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/207096\n\nThis continues the work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES returns a 200 response containing an error field when we\nwait for the update mappings task. This case wasn't being handled. This\nPR handles that case, when we find a `search_phase_execution_exception`\nin the ES response we return a retryable error that sends us back to the\nupdate mappings state. It does it for both migration algorithms, the\npriority is ZDT but seemed like a nice to have in both.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"49380143432b654cf1b849d8c77b3abc2fb3aeb4"}}]}] BACKPORT--> Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| core-saved-objects-api-browser | ||
| core-saved-objects-api-server | ||
| core-saved-objects-api-server-internal | ||
| core-saved-objects-api-server-mocks | ||
| core-saved-objects-base-server-internal | ||
| core-saved-objects-base-server-mocks | ||
| core-saved-objects-browser | ||
| core-saved-objects-browser-internal | ||
| core-saved-objects-browser-mocks | ||
| core-saved-objects-common | ||
| core-saved-objects-import-export-server-internal | ||
| core-saved-objects-import-export-server-mocks | ||
| core-saved-objects-migration-server-internal | ||
| core-saved-objects-migration-server-mocks | ||
| core-saved-objects-server | ||
| core-saved-objects-server-internal | ||
| core-saved-objects-server-mocks | ||
| core-saved-objects-utils-server | ||
| docs/openapi | ||