[SERVER-56160] Exclude $setWindowFields from API Version 1 Created: 19/Apr/21  Updated: 29/Oct/23  Resolved: 20/Apr/21

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Query Language
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-56161 Add $setWindowFields to API Version 1 Backlog
Documented
is documented by DOCS-14372 Investigate changes in SERVER-56160: ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Optimization 2021-05-03
Participants:

 Description   

The window functions are considered somewhat unstable while we validate with the beta program whether some of our design and semantic choices were reasonable. For example, what should the behavior be with unexpected types or null values? Or when combinations of arguments don't clearly interact well.

As one concrete example, to quote David Percy:

For range-based / time-based bounds, the sortBy field has to be a number / date, respectively. If the current document's sortBy is the wrong type, then it gets assigned 'null'. But maybe it would be clearer to throw an error instead?

We plan to add $setWindowFields to API Version 1 in the coming months as we gather some confidence on these decisions.



 Comments   
Comment by Githook User [ 20/Apr/21 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-56160 Exclude $setWindowFields from API Version 1
Branch: master
https://github.com/mongodb/mongo/commit/1203b3cf635f14937b93ff60386a2067e73b4b01

Generated at Thu Feb 08 05:38:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.