[SERVER-71011] ShardingCatalogManager::withTransaction is no longer needed Created: 02/Nov/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Enrico Golfieri | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
ShardingCatalogManager::withTransaction it's an old helper function to run a lambda within a transaction locally to the config server. However, with the introduction of the new transaction API, we no longer need that. For easy refactoring, this helper function can be used as replacement where withTransaction is called. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 01/Jun/23 ] |
|
There is a problem with that helper, it does not use a resource yielder, I think we don't need to use that API, but on each withTransaction call analyze the context and use the transaction API. |
| Comment by Enrico Golfieri [ 03/Nov/22 ] |
|
sergi.mateo-bellido@mongodb.com So far it has been used only here |
| Comment by Sergi Mateo Bellido [ 03/Nov/22 ] |
|
enrico.golfieri@mongodb.com, can you list here all the usages of the withTransaction API? |