[SERVER-72504] Futher investigate the cause of blacklisting jstests/core/index_key_expression.js in some sharding pasthrough Created: 04/Jan/23 Updated: 29/Oct/23 Resolved: 15/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Rishab Joshi (Inactive) | Assignee: | Rishab Joshi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QE 2023-01-23 |
| Participants: |
| Description |
|
The jstests/core/index_key_expression.js failed in some of the sharding passthrough with the error - "The field '$const' is not valid for an index specification.", where the extra $const specifier gets prepended to the index spec in some cases, as in:
The $const causes the index-specification validation code to flag this spec as invalid; hence, the JS test fails with an unexpected error. This could be a legit issue and this ticket is about investigating the cause. |
| Comments |
| Comment by Githook User [ 15/Jan/23 ] |
|
Author: {'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}Message: |