Fix Snapshot Status API Docs Test (#59902) (#59908)

The clock resolution for this API is our default 200ms. It is unlikely but
possible that a shard snapshot starts and ends on separate clock ticks and that breaks the test.
Just allowing any value here seems fine to me (seems we can't match for integer specifically).
This commit is contained in:
Armin Braun 2020-07-20 18:43:40 +02:00 committed by GitHub
parent 515b53d297
commit e16e565c5e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions

View File

@ -389,6 +389,7 @@ GET /_snapshot/my_repository/snapshot_2/_status
// TESTRESPONSE[s/"total" : 10/"total" : $body.snapshots.0.shards_stats.total/]
// TESTRESPONSE[s/"start_time_in_millis" : 1594829326691/"start_time_in_millis" : $body.snapshots.0.stats.start_time_in_millis/]
// TESTRESPONSE[s/"time_in_millis" : 205/"time_in_millis" : $body.snapshots.0.stats.time_in_millis/]
// TESTRESPONSE[s/"time_in_millis" : 0/"time_in_millis" : $body.$_path/]
// TESTRESPONSE[s/"file_count" : 3/"file_count" : $body.snapshots.0.stats.incremental.file_count/]
// TESTRESPONSE[s/"file_count" : 4/"file_count" : $body.snapshots.0.stats.total.file_count/]
// TESTRESPONSE[s/"size_in_bytes" : 5969/"size_in_bytes" : $body.snapshots.0.stats.incremental.size_in_bytes/]