We uncovered a bug on the timeseries insert path. When we have an geosphere index on a timeseries collection (example {loc: "2dsphere"}), the second time we insert a document into a given bucket, we treat it as an "update" of the bucket rather than a new "insert". Because we go the update path, we skip some logic that updates the underlying indexes.
In the geo-specific case, this does cause a bug where we may miss results in a query if the query should match an index key from the second document inserted to the bucket but not the first document.
- is caused by
-
SERVER-83140 Implement DocDiff support for BSONColumn
-
- Closed
-
- related to
-
SERVER-113671 PQS does not apply $natural hint to $geoIntersects queries
-
- Closed
-
-
SERVER-112643 Add generic DocumentDiffReader::next()
-
- Closed
-