[SERVER-45457] Allow disabling system.js on a per-expression basis Created: 09/Jan/20 Updated: 29/Oct/23 Resolved: 21/Feb/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: | Katherine Wu (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2020-02-10, Query 2020-02-24 |
| Participants: |
| Description |
|
We would like to move away from system.js for new Javascript operators such as $function and $accumulator. But for backwards compatibility we need to continue to support it for $where and MapReduce, even though these will desugar to $function and $accumulator. The switch should be per-expression, not per query: in a query containing both $where and $function, the $where expression should see system.js functions but the $function expression should not. |
| Comments |
| Comment by Githook User [ 21/Feb/20 ] |
|
Author: {'name': 'Katherine Wu', 'username': 'kaywux', 'email': 'katherine.wu@mongodb.com'}Message: create mode 100644 jstests/core/system_js_access.js |