[SERVER-28678] The explain command should reject explained commands containing readConcern or writeConcern Created: 07/Apr/17 Updated: 29/May/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, the explain command ignores any readConcern or writeConcern fields contained in the explained commands:
Consider rejecting these commands, as read/write concern are not relevant to evaluating the query plan. This would be a minor backwards breaking change for drivers, some of which currently would send an explain command with read/write concern fields present in the explained command. |
| Comments |
| Comment by Githook User [ 29/May/23 ] |
|
Author: {'name': 'Jérôme Tamarelle', 'email': 'jerome.tamarelle@mongodb.com', 'username': 'GromNaN'}Message: ReadConcern is relevant for query plan evaluation, not WriteConcern. The option is sent only for operations that support ReadConcern. |
| Comment by Asya Kamsky [ 21/Oct/20 ] |
|
jeff.yemin that's not right: > read/write concern are not relevant to evaluating the query plan Read concern available (as opposed to local) does not use SHARDING_FILTER so the plan would be different. |