diff options
author | Arun Banala <arun.banala@mongodb.com> | 2020-05-08 11:29:17 +0100 |
---|---|---|
committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2020-05-08 14:36:44 +0000 |
commit | 2d00fa0708dc62593d387cc09eab46f5a2ba8c9f (patch) | |
tree | 1694e2d573d5c465811ffc06245533a263f91f52 /jstests/core | |
parent | a7ff5838b5a4bcb4881a08c5dafce671c3b54940 (diff) | |
download | mongo-2d00fa0708dc62593d387cc09eab46f5a2ba8c9f.tar.gz |
SERVER-44599 Blacklist tests impacted by the sort optimization in multiversion suites
Diffstat (limited to 'jstests/core')
-rw-r--r-- | jstests/core/covered_index_sort_no_fetch_optimization.js | 20 | ||||
-rw-r--r-- | jstests/core/hashed_index_sort.js | 7 |
2 files changed, 18 insertions, 9 deletions
diff --git a/jstests/core/covered_index_sort_no_fetch_optimization.js b/jstests/core/covered_index_sort_no_fetch_optimization.js index 5fc1e00f8ef..964da9d67db 100644 --- a/jstests/core/covered_index_sort_no_fetch_optimization.js +++ b/jstests/core/covered_index_sort_no_fetch_optimization.js @@ -1,10 +1,16 @@ -// Confirms that blocking sorts are covered when the index contains the sort key. -// For example, if we have an index on {a:1, b:1} and a sort on {b:1}, and a projection of only -// field 'b', we can sort using only the existing index keys, without needing to do a fetch. - -// Queries on a sharded collection can't be covered when they aren't on the shard key. The document -// must be fetched to support the SHARDING_FILTER stage. -// @tags: [assumes_unsharded_collection] +/** + * Confirms that blocking sorts are covered when the index contains the sort key. For example, if we + * have an index on {a:1, b:1} and a sort on {b:1}, and a projection of only field 'b', we can sort + * using only the existing index keys, without needing to do a fetch. + * + * Queries on a sharded collection can't be covered when they aren't on the shard key. The document + * must be fetched to support the SHARDING_FILTER stage. + * @tags: [ + * assumes_unsharded_collection, + * # Sort optimizations added for hashed indexes in 4.6 can generate a different plan. + * requires_fcv_46 + * ] + */ (function() { "use strict"; diff --git a/jstests/core/hashed_index_sort.js b/jstests/core/hashed_index_sort.js index f4119fd5ae1..eeaf793904c 100644 --- a/jstests/core/hashed_index_sort.js +++ b/jstests/core/hashed_index_sort.js @@ -3,7 +3,10 @@ * the 'find' command. The test verifies compound hashed index with hashed prefix and non-hashed * prefix. * @tags: [ - * assumes_unsharded_collection, + * assumes_unsharded_collection, + * # Sort optimizations added in 4.6 can generate a different plan in the presence of equality + * # predicates. + * requires_fcv_46 * ] */ (function() { @@ -194,4 +197,4 @@ validateFindCmdOutputAndPlan({ expectedOutput: [{c: 2}], expectedStages: ["IXSCAN", "FETCH", "SORT"] }); -})();
\ No newline at end of file +})(); |