[SERVER-73465] Updates during column store index build can result in no-op side writes Created: 30/Jan/23  Updated: 29/Oct/23  Resolved: 16/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Justin Seyster Assignee: Justin Seyster
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QE 2023-02-06, QE 2023-02-20
Participants:
Linked BF Score: 125

 Description   

When a column store index is limited to a subset of columns (either by a columnstoreProjection or by "foo.$**"-style notation), it is possible for a document replacement update to get forwarded to the index even when it does not modify any of the indexed columns. When this happens during bulk building, it results in a "side write" that has no entries.

That behavior is semantically correct but trips an invariant when it eventually gets processed. There is no need for these no-op entries, though, and it is a simple to change the index update code so that it does not write them.



 Comments   
Comment by Githook User [ 01/Feb/23 ]

Author:

{'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com', 'username': 'jseyster'}

Message: SERVER-73465 Updates during column store index build can result in no-op side writes
Branch: master
https://github.com/mongodb/mongo/commit/923f10421df339783d3f1baeb60be5bac3180fa3

Generated at Thu Feb 08 06:24:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.