IDEA: build another test like CCSDuelIT (except I would make it an IT test, not a qa test, so pattern it after CCSDuelIT in testing pattern, but use CrossClusterAsyncSearchIT as the guide for how to implement/structure the test). This “duel” would be between async local-only and async CCS tests. Test every response object (such as is_partial, which motivated this test) to make sure they are either the same between the two or legitmately different. (Example of legimately different: there is no _cluster/details section for local-only searches.).
The goal is to prevent future changes from letting local-only and cross-cluster searches unintentinally diverge in behavior.
Description
Focus particularly on async-search.
IDEA: build another test like CCSDuelIT (except I would make it an IT test, not a qa test, so pattern it after CCSDuelIT in testing pattern, but use CrossClusterAsyncSearchIT as the guide for how to implement/structure the test). This “duel” would be between async local-only and async CCS tests. Test every response object (such as is_partial, which motivated this test) to make sure they are either the same between the two or legitmately different. (Example of legimately different: there is no _cluster/details section for local-only searches.).
The goal is to prevent future changes from letting local-only and cross-cluster searches unintentinally diverge in behavior.