From eedf8e06bc16c6c60be9cf90f6600d7c713ccda0 Mon Sep 17 00:00:00 2001 From: Julie Tibshirani Date: Mon, 12 Jul 2021 10:19:50 -0700 Subject: [PATCH] Loosen checks in REST test for PIT slicing Since the index may have more than one shard, we can't always predict how many documents will fall in each slice. This PR simply removes the checks, since we already test the slicing logic extensively in an integration test. The REST test is now just a sanity check for the API. --- .../rest-api-spec/test/search/350_point_in_time.yml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search/350_point_in_time.yml b/rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search/350_point_in_time.yml index f48b8e2895d5f..b3ad192710cdf 100644 --- a/rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search/350_point_in_time.yml +++ b/rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search/350_point_in_time.yml @@ -136,8 +136,8 @@ setup: --- "point-in-time with slicing": - skip: - version: "all" - reason: "https://github.com/elastic/elasticsearch/issues/75212" + version: " - 7.14.99" + reason: "support for slicing was added in 7.15" - do: open_point_in_time: index: test @@ -158,9 +158,6 @@ setup: pit: id: "$point_in_time_id" - - match: {hits.total.value: 2 } - - length: {hits.hits: 1 } - - do: close_point_in_time: body: