[ESQL] Skip CCQ tests when remote skipped due to connect_transport_exception#154977
Draft
hawkhuang-collab wants to merge 3 commits into
Draft
[ESQL] Skip CCQ tests when remote skipped due to connect_transport_exception#154977hawkhuang-collab wants to merge 3 commits into
hawkhuang-collab wants to merge 3 commits into
Conversation
…ception When a remote cluster is unavailable during query execution, EsqlCCSUtils returns a 200 OK with is_partial=true and the remote cluster marked status=skipped with a connect_transport_exception failure. CCQ csv-spec tests for lookup indices are particularly vulnerable because they query remote-only (no local fallback), so any transient remote outage produces an empty result set that fails the row-count assertion. Instead of failing in assertNotPartial, detect this specific pattern and skip the test via JUnit Assume, treating it as an infrastructure flake rather than a product failure.
hawkhuang-collab
added
>test
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When a remote cluster is unavailable during query execution, EsqlCCSUtils returns a 200 OK with is_partial=true and the remote cluster marked status=skipped with a connect_transport_exception failure. CCQ csv-spec tests for lookup indices are particularly vulnerable because they query remote-only (no local fallback), so any transient remote outage produces an empty result set that fails the row-count assertion.
Instead of failing in assertNotPartial, detect this specific pattern and skip the test via JUnit Assume, treating it as an infrastructure flake rather than a product failure.