[SERVER-82454] Remove 'expects_explicit_underscore_id_index' tag from sbe_plan_cache_does_not_block_range_deletion.js Created: 26/Oct/23 Updated: 09/Nov/23 Resolved: 09/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Denis Grebennicov | Assignee: | Kevin Cherkauer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quick-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QE 2023-11-13 |
| Participants: |
| Description |
|
While investigating a BF, I stumbled on https://github.com/mongodb/mongo/blob/master/jstests/sharding/sbe_plan_cache_does_not_block_range_deletion.js#L7-L9 which adds a tag, which ensures this test is not run with SBE, as previously SBE was not supporting clustered collection scans. As this is no longer true, I assume we can remove this tag and gain additional test coverage. I am wondering if there are other places, where we avoid running specific tests, due to assumption of SBE not supporting clustered coll scans. |
| Comments |
| Comment by Githook User [ 09/Nov/23 ] |
|
Author: {'name': 'Kevin Cherkauer', 'email': 'kevin.cherkauer@mongodb.com', 'username': 'kevin-cherkauer'}Message: |