[DOCS-16258] Doc of $setWindowFields should explain any guarantees for the output order of documents Created: 11/Jul/23  Updated: 13/Nov/23  Resolved: 08/Nov/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 5.0.0, 6.0.0, 7.1.0, 7.0.0
Fix Version/s: Server_Docs_20231113

Type: Task Priority: Minor - P4
Reporter: Andre Spiegel Assignee: Jason Price
Resolution: Done Votes: 0
Labels: quick-win
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 13 weeks, 5 days ago
Story Points: 3

 Description   

The documentation of $setWindowFields should specify whether there are any guarantees for the output order of documents. Intuitively, you would assume that the documents are ordered by { partitionBy : 1, sortBy : 1 }, and in practice, this seems to be the case. However, this is not explicitly mentioned in the documentation, so developers cannot rely on it.

Edit: Here is the link to the page: https://www.mongodb.com/docs/manual/reference/operator/aggregation/setWindowFields/



 Comments   
Comment by Jason Price [ 03/Nov/23 ]

https://github.com/10gen/docs-mongodb-internal/pull/5186

Comment by Andre Spiegel [ 03/Nov/23 ]

jason.price@mongodb.com Conversation with the developers confirmed that a user cannot make any assumptions about the order of documents coming out of $setWindowFields. Please add a sentence to the documentation that clarifies this. The best place to add this is probably in the Behavior section.

Comment by Jason Price [ 29/Sep/23 ]

Per a Slack convo with Andre on Sep 29, 2023:

"I have been talking to the engineers about it, but the conversation stalled. Please keep it open, and I will get back to you about the solution as soon as possible."

Comment by Jason Price [ 29/Sep/23 ]

andre.spiegel@mongodb.com any updates? Or, can we close this? Thanks.

Comment by Jason Price [ 07/Aug/23 ]

Placing into blocked status as it is awaiting further information.

Generated at Thu Feb 08 08:14:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.