-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Query Optimization
-
(copied to CRM)
update operations can currently FETCH the same document multiple times. This happens when the index being used includes a key that the update is modifying and the modification places the new entry later in the index relative to the traversal that is happening. We successfully use the record ids to avoid modifying the document multiple times, but we currently FETCH it more than once. This seems unnecessary as we should be able to use the record id in the index to confirm that no further work is necessary for the document.