[SERVER-45209] Allow $merge in aggregations in multi-document transactions Created: 17/Dec/19  Updated: 05/Oct/23

Status: Backlog
Project: Core Server
Component/s: Catalog
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Garaudy Etienne
Resolution: Unresolved Votes: 6
Labels: sharding-product-sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-54462 Support $merge stage in transaction Closed
Sprint: Execution Team 2021-02-08, Execution Team 2021-02-22, Execution Team 2021-03-08, Execution Team 2021-03-22
Participants:
Case:

 Description   

This is another case of implicit collection creation inside multi-document transactions, and will make use of the work in SERVER-43859 and SERVER-44139.



 Comments   
Comment by Garaudy Etienne [ 29/Sep/23 ]

alblosi@gmail.com This ticket depends on another prerequisite ticket that we're tackling in October. Will revisit with my team next week to see if we can now get a better estimate.

Comment by Alberto Losi [ 06/Jun/23 ]

Hi garaudy.etienne@mongodb.com, do you have any updates on this issue? many thanks

Comment by Alberto Losi [ 31/Mar/23 ]

Hi garaudy.etienne@mongodb.com 

Our use case is related to the operation that are performed by our application that have a very strict timeout on execution time:

Some commands performs operations on several collections and run several aggregation pipelines to update matterialized views.
We want collections to be always synchronized to the materialized views event though some errors occur (e.g. application timeout)

Consider the following scenario:
We have N different collections that are updated by a single command

  • Coll1
  • Coll2
  • ...
  • CollN

And we have N different materialized view based on data from the previous collections

  • MV1
  • MV2
  • ..
  • MVN

Consider a scenario in which the application timeout expires during aggregation pipeline execution for example during the update of the MV2:

In this case we want the transaction to rollabck all modification performed on collections and on already updated materialized views (In the example Coll1..CollN and MV1)

Comment by Garaudy Etienne [ 30/Mar/23 ]

alblosi@gmail.com can you share some details on what you're trying to achieve with this capability?

Comment by Garaudy Etienne [ 15/Mar/23 ]

Hi alblosi@gmail.com, will discuss it with the engineering team this week and get back to you on the timeline.

Comment by Alberto Losi [ 15/Mar/23 ]

Hi, is there any timeline for this feature? thanks

Comment by Eric Milkie [ 26/May/20 ]

The work to support this isn't scheduled yet, so it is unlikely to be included in the next release (4.6).

Comment by Olivier Boudet [ 23/May/20 ]

Hello, is there a roadmap for this feature ?

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