[SERVER-36279] Change the explain format for sharded aggregations to accomodate $exchange Created: 25/Jul/18  Updated: 29/Oct/23  Resolved: 26/Sep/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Diagnostics
Affects Version/s: None
Fix Version/s: 4.1.4

Type: Task Priority: Major - P3
Reporter: Kyle Suarez Assignee: Martin Neupauer
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35905 Plug pieces together to perform a dis... Closed
Related
related to SERVER-43429 Complete TODO listed in SERVER-36279 Closed
related to SERVER-44202 Complete TODO listed in SERVER-36279 Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2018-09-10, Query 2018-09-24, Query 2018-10-08
Participants:

 Description   

In a world where $exchange could be inserted theoretically anywhere in a sharded aggregation, it won't make sense to always present the "splitPipeline" in aggregation explain as a "shardsPart" and "mergerPart".

One potential format is to break up the pipeline into "bubbles", where each one is separated by $exchange. At the exchange points, we could expose detail on which producers are feeding each consumer, to give a sense of how the routing is occurring.



 Comments   
Comment by Githook User [ 26/Sep/18 ]

Author:

{'name': 'Martin Neupauer', 'email': 'martin.neupauer@mongodb.com', 'username': 'MartinNeupauer'}

Message: SERVER-36279 Change the explain format for sharded aggregations to accomodate $exchange
Branch: master
https://github.com/mongodb/mongo/commit/b6324b30cac621dde4c96d91b52fa870600a72d5

Generated at Thu Feb 08 04:42:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.