[SERVER-46311] $$IS_MR and $$JS_SCOPE access crashes the server Created: 21/Feb/20 Updated: 29/Oct/23 Resolved: 27/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 4.3.4 |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jacob Evans | 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 |
| Operating System: | ALL |
| Sprint: | Query 2020-02-24, Query 2020-03-09 |
| Participants: |
| Description |
|
Please consider passing these to shards with a different mechanism since logically using runtime constants is a bit of a mismatch. These are expected to be user-visible. As for why this happens this switch at least is not expecting the new constants. |
| Comments |
| Comment by Githook User [ 26/Feb/20 ] |
|
Author: {'name': 'Katherine Wu', 'username': 'kaywux', 'email': 'katherine.wu@mongodb.com'}Message: create mode 100644 jstests/aggregation/variables/runtime_constants.js |
| Comment by James Wahlin [ 24/Feb/20 ] |
|
Let's use this ticket to address the crash / missing condition in the switch statement. jacob.evans we can discuss the motivation for making these runtime constants and potential alternatives. I suggest we break out any work to change into a separate ticket. |