[SERVER-63479] Correct $$SEARCH_META ban in sharded environments Created: 09/Feb/22 Updated: 29/Oct/23 Resolved: 24/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.8, 5.3.1, 4.4.15 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Backport Requested: |
v5.3, v5.0, v4.4
|
||||||||||||||||
| Sprint: | QO 2022-03-07, QO 2022-03-21, QO 2022-04-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If the feature flag is disabled, $$SEARCH_META should not be allowed on sharded collections. Currently this is accomplished here during runtime. We should change this to be checked earlier when detecting that we are in a sharded collection w/o the feature flag. |
| Comments |
| Comment by Githook User [ 01/Jun/22 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 01/Jun/22 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 19/Apr/22 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 19/Apr/22 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |