[SERVER-46098] Explore MaxTimeMS handling in thread local scope Created: 12/Feb/20 Updated: 29/Oct/23 Resolved: 14/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Cox (Inactive) | Assignee: | James Wahlin |
| 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 |
| Participants: |
| Description |
|
Replacing PooledScope with thread local scope doesn't allow for proper handling of .maxTimeMS() in a find query that contains a $where expression. This caused two test suites to fail that were subsquently blacklisted in The work here should investigate how to correctly support MaxTimeMS in the js thread local scope machinery. See |
| Comments |
| Comment by Githook User [ 14/Feb/20 ] |
|
Author: {'name': 'James Wahlin', 'username': 'jameswahlin', 'email': 'james@mongodb.com'}Message: With this change MaxTimeMS handling will work correctly for aggregation JavaScript |