Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84470

Allow $lookup to target an unsplittable collection on a primary shard within a multi-document transaction

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc3
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-04-15, CAR Team 2024-04-29, QE 2024-01-08, QE 2024-01-22
    • 153

      As explained in SERVER-46373 currently $lookup is not allowed to target a sharded collection in a multi document transaction due to 2 known reasons:

      • That a shard targeting itself will deadlock trying to re-acquire the same session
      • That if a different shard needs to be targeted, the shard does not know how to correctly start the multi-doc txn on that other shard.

      After SERVER-81190 unsharded collection will be tracked and $lookup as a consequence won't be allowed on a unsharded collection as well (within a transaction)

      The goal of this ticket is to allow $lookup on an unsplittable collection if that collection is still on the primary. This is just a temporary fix before SERVER-46373 to enable SERVER-81190 to be merged and start tracking collections.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: