[SERVER-77469] Propagate QuerySettings from mongos to the shards Created: 25/May/23 Updated: 16/Nov/23 Resolved: 16/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Denis Grebennicov | Assignee: | Denis Grebennicov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | M1, auto-reverted | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | QE 2023-10-30, QE 2023-11-13, QE 2023-11-27 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 160 | ||||||||||||
| Comments |
| Comment by Githook User [ 15/Nov/23 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: Before this change, query settings were only looked up on mongod, which means that query settings will not be applied to find queries that were modified on mongos. In order to fix this issue, query settings will be looked up on mongos in sharded cluster and on mongod in replica set deployments. Upon the lookup, query settings will be propagated to the shards as command's new 'querySettings' attribute (marked as unstable). In addition, as a part of this change, the encoding of a CanonicalQuery into a QueryShapeString will omit the 'hint' field if it is made redundant by the matching query setting. |
| Comment by Githook User [ 13/Nov/23 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 98d757f948e0d09eb85da5597ca43f79c545c91b. |
| Comment by Githook User [ 13/Nov/23 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: Before this change, query settings were only looked up on mongod, which means that query settings will not be applied to find queries that were modified on mongos. In order to fix this issue, query settings will be looked up on mongos in sharded cluster and on mongod in replica set deployments. Upon the lookup, query settings will be propagated to the shards as command's new 'querySettings' attribute (marked as unstable). In addition, as a part of this change, the encoding of a CanonicalQuery into a QueryShapeString will omit the 'hint' field if it is made redundant by the matching query setting. |
| Comment by Githook User [ 11/Nov/23 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 39dd12e2569f1189f8ae6d95f2148d87d9bf7086. |
| Comment by Githook User [ 10/Nov/23 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: Before this change, query settings were only looked up on mongod, which means that query settings will not be applied to find queries that were modified on mongos. In order to fix this issue, query settings will be looked up on mongos in sharded cluster and on mongod in replica set deployments. Upon the lookup, query settings will be propagated to the shards as command's new 'querySettings' attribute (marked as unstable). In addition, as a part of this change, the encoding of a CanonicalQuery into a QueryShapeString will omit the 'hint' field if it is made redundant by the matching query setting. |