Repository navigation
Fix isErrorResponse when cluster details are provided - #166544
Conversation
| return ( | ||
| !response || | ||
| !response.rawResponse || | ||
| (!response.isRunning && !!response.isPartial && !response.rawResponse?._clusters?.details) |
There was a problem hiding this comment.
Just for reference:
This basically determines that ES will handle the isPartial flag differently for CCS?
There was a problem hiding this comment.
Yeah, I should add a comment there. Basically, the behavior for CCS with ccs_minimize_roundtrips=true is to set is_partial to true if the search is complete but there are some shard failures (and thus partial results), then have details about the failures inside the _clusters.details section. This will also likely be the behavior of CCS with ccs_minimize_roundtrips=false and non-CCS after elastic/elasticsearch#98913 is resolved.
There was a problem hiding this comment.
I've added some comments to the code in 0859897.
There was a problem hiding this comment.
This will also likely be the behavior of CCS with ccs_minimize_roundtrips=false
Chatted offline with @quux00 and he confirmed this is correct for the non-CCS situation (this work is still pending), but already merged for the CSS-part in 8.11/main.
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
davismcphee
left a comment
There was a problem hiding this comment.
Thanks for fixing this! I confirmed that without the fix in 8.10, an error is shown. And with the fix in this PR, a warning is shown that matches the local cluster behaviour.
We should try to get confirmation from someone in Security who encountered the issue too if possible, but I don't want to hold hold this up so I'm approving now for when we're ready.
davismcphee
left a comment
There was a problem hiding this comment.
Oops, I didn't realize the build failed before submitting my review... I guess we'll need to investigate what's going on there first.
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
cc @yuliacech @stephmilovic Would be great if you could take a look at this as well from Security-side. Thx! |
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Page load bundle
History
To update your PR or re-run it, just comment with: cc @lukasolson |
|
Is there risk this might have impact for the visualizations team? And is there an impact for CSS if the remote clusters are still 8.9.x and local is 8.10.x ? |
I don't think there is but @elastic/kibana-visualizations will know better |
|
@elasticmachine merge upstream |
stephmilovic
left a comment
There was a problem hiding this comment.
This clears the partial results error in Security Solution. Thanks for the quick fix, LGTM!
@lukasolson I want to make sure we don't lose sophie's question here, have we validated this with clusters on different versions? |
I just verified that this fix works for this scenario as well (and that it is also broken in this scenario without this fix). |
…ic#166544) ## Summary Fixes elastic#166528. ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. When forming the risk matrix, consider some of the following examples and how they may potentially impact the change: | Risk | Probability | Severity | Mitigation/Notes | |---------------------------|-------------|----------|-------------------------| | Multiple Spaces—unexpected behavior in non-default Kibana Space. | Low | High | Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces. | | Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks. | High | Low | Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure. | | Code should gracefully handle cases when feature X or plugin Y are disabled. | Medium | High | Unit tests will verify that any feature flag or plugin combination still results in our service operational. | | [See more potential risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) | ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary Cherry picks #166544 into main. Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
Fixes #166528.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers