Ensure cluster-wide parameters mechanism correctness (when working with query settings parameter)
(SERVER-78801)
|
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Denis Grebennicov | Assignee: | Romans Kasperovics |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | M2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | QE 2023-07-24, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13, QE 2023-11-27, QE 2023-12-11, QE 2023-12-25, QE 2024-01-08 | ||||
| Participants: | |||||
| Linked BF Score: | 4 | ||||
| Comments |
| Comment by Githook User [ 21/Dec/23 ] | |||||||
|
Author: {'name': 'romanskas', 'email': '30618745+romanskas@users.noreply.github.com', 'username': 'romanskas'}Message:
Until now, a new value of a cluster parameter was just replacing the old GitOrigin-RevId: f5f35648c676f7dd132ba69d34bbd5251b71a2e1 | |||||||
| Comment by Billy Donahue [ 20/Sep/23 ] | |||||||
|
Thanks! | |||||||
| Comment by Romans Kasperovics [ 14/Sep/23 ] | |||||||
|
Hi billy.donahue@mongodb.com, sorry and thank you for noticing! Yes, this sneak in by mistake, and yes, I used it for printf-debugger | |||||||
| Comment by Billy Donahue [ 13/Sep/23 ] | |||||||
|
Hi. If you could follow up and remove it, I'd appreciate it. This will clear the way for a migration from boost::optional to std::optional (which has no analogous feature). Basically, it's just a replacement:
If the code is phrased this way, then it will continue to work if someOptional is changed from boost::optional to std::optional. | |||||||
| Comment by Githook User [ 30/Aug/23 ] | |||||||
|
Author: {'name': 'Romans Kasperovics', 'email': 'romans.kasperovics@mongodb.com', 'username': 'romanskas'}Message: Until now, a new value of a cluster parameter was just replacing the old one. |