-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: ecosystem
-
Labels:
-
Environment:
*Location*: https://docs.mongodb.com/ecosystem/use-cases/pre-aggregated-reports-mmapv1/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
*Referrer*: https://docs.mongodb.com/manual/core/data-model-operations/
*Screen Resolution*: 1366 x 768
*Location*: https://docs.mongodb.com/ecosystem/use-cases/pre-aggregated-reports-mmapv1/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 *Referrer*: https://docs.mongodb.com/manual/core/data-model-operations/ *Screen Resolution*: 1366 x 768
In order to update the value in minute #1349, MongoDB must skip over all 1349 entries before it.
is actually 1,439 per the figures and text leading up to it..