[SERVER-45455] Use a merging shard to prevent JS failing on mongos Created: 09/Jan/20 Updated: 15/Jan/20 Resolved: 15/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | James Wahlin |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When we split a pipeline into the shardsPart and mergerPart, if the mergerPart contains Javascript operators such as $function, $accumulate, or $_internalJsEmit, we need to do the merge on a shard instead of on mongos, because today we don't run JS on mongos. |
| Comments |
| Comment by James Wahlin [ 15/Jan/20 ] |
|
Closing this ticket in favor of allowing Javascript to run on mongos under |