In a multi-document transaction where an index is created (see SERVER-44849), if a subsequent insert within the same transaction has a mutikey field that would convert the recently created index into a multikey index, the function IndexCatalogEntryImpl::setMultikey() would fail within this side transaction introduced in SERVER-41766.
One possible cause is that the index created in the parent transaction is not visible to the side transaction.
- is related to
-
SERVER-41766 Secondary may encounter prepare conflict when applying write that sets the multikey flag
-
- Closed
-
-
SERVER-44849 Allow createIndexes inside multi-document transactions if on an empty collection created in the same transaction or on a non-existing collection
-
- Closed
-
- related to
-
-
- Closed
-