[DOCS-15256] [SERVER] Investigate changes in SERVER-63479: Correct $$SEARCH_META ban in sharded environments Created: 19/Apr/22 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.8, 5.3.1, 4.4.15 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, feature, query, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 1 year, 36 weeks ago | ||||||||||||||||
| Description |
|
Original Downstream Change Summary While this ticket does not change the promised behavior, it previously would have been possible to run certain search aggregation stages in sharded environments that would have returned incorrect results. This ticket correctly bans those pipelines, but some users may see their queries fail with the new error. The feature banned by this ticket is enabled in 6.0 Description of Linked TicketIf 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 Education Bot [ 01/Jun/22 ] |
|
Fix Version updated for upstream |
| Comment by Jess Mokrzecki [ 19/Apr/22 ] |
|
Fix Version updated for upstream |