[SERVER-55481] Update doc_diff::applyDiff to determine when it can stop continually checking if the data mightBeIndexed Created: 24/Mar/21  Updated: 29/Oct/23  Resolved: 20/Apr/21

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

Type: Task Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from SERVER-55350 Investigate single-threaded timeserie... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-04-19, Execution Team 2021-05-03
Participants:

 Description   

in timeseries collections, we often append lots of elements to array fields in the same diff when updating a bucket. Each time, we check if we check if the field mightBeIndexed. In such cases, we only really need to check once, and we can save the negative result in the same way we currently save the positive result. This will likely require changing the state from a bool to an enum with three entries (yes, no, undetermined).



 Comments   
Comment by Githook User [ 20/Apr/21 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-55481 Avoid repeatedly checking whether indexes are affected for the same path when inserting fields in the document diff applier
Branch: master
https://github.com/mongodb/mongo/commit/22ee3f2282ca183d37598e0638cdd6ce4fdf21d2

Generated at Thu Feb 08 05:36:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.