[SERVER-76749] runTransactionOnShardingCatalog should not assign the current operation context session id to the new operation context Created: 02/May/23 Updated: 02/Jan/24 Resolved: 04/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0-rc0, 7.1.0-rc0 |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Enrico Golfieri | Assignee: | Enrico Golfieri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||
| Sprint: | Sharding EMEA 2023-05-15 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Right now the runTransactionOnShardingCatalog assigns the operation context 's session id to the new operation context in case the input osi is empty. This is wrong becauseĀ
|
| Comments |
| Comment by Githook User [ 04/May/23 ] |
|
Author: {'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}Message: ( cherry picked from b98740e2d27df0fa95632a1ac40adf140512e51c ) |
| Comment by Githook User [ 04/May/23 ] |
|
Author: {'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}Message: |