diff options
| author | Faustoleyva54 <fausto.leyva@mongodb.com> | 2022-11-24 04:54:22 +0000 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2022-11-24 05:23:36 +0000 |
| commit | 88f4a04a3e80a139d000caa7f212f5faa168f7e4 (patch) | |
| tree | 1b8a98dbfa3ccfaa4f99fd9e80176b7f1dcbe712 /src/mongo/s/query/cluster_aggregate.cpp | |
| parent | eaafcf8243e7ca4770bbaca00f46b569b474f2c1 (diff) | |
| download | mongo-88f4a04a3e80a139d000caa7f212f5faa168f7e4.tar.gz | |
SERVER-70258 Test custom bucketMaxSpanSeconds and bucketRoundingSeconds values with sharding
Diffstat (limited to 'src/mongo/s/query/cluster_aggregate.cpp')
| -rw-r--r-- | src/mongo/s/query/cluster_aggregate.cpp | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/mongo/s/query/cluster_aggregate.cpp b/src/mongo/s/query/cluster_aggregate.cpp index f50caecb14e..767da787f0b 100644 --- a/src/mongo/s/query/cluster_aggregate.cpp +++ b/src/mongo/s/query/cluster_aggregate.cpp @@ -590,9 +590,9 @@ Status ClusterAggregate::retryOnViewError(OperationContext* opCtx, nsStruct.executionNss = resolvedView.getNamespace(); // For a sharded time-series collection, the routing is based on both routing table and the - // granularity value. We need to make sure we use the granularity value of the same version as - // the routing table, instead of the one attached in the view error. This way the shard - // versioning check can correctly catch stale routing information. + // bucketMaxSpanSeconds value. We need to make sure we use the bucketMaxSpanSeconds of the same + // version as the routing table, instead of the one attached in the view error. This way the + // shard versioning check can correctly catch stale routing information. boost::optional<ChunkManager> snapshotCm; if (nsStruct.executionNss.isTimeseriesBucketsCollection()) { auto executionNsRoutingInfoStatus = |