-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Timeseries updates do a rewrite of the query and modifier field of the input update request. This is true for both legacy and viewless timeseries collections. Our current query stats update system would record the parsed update after the rewrite on mongod which is not what we want, so we skip recording query stats for now.
We should record the initial update that the user gave. This will make sure the queryShapeHash matches for nodes that don't know the collection is a timeseries collection (and don't do the rewrite) and those that do the timeseries rewrite (see TODOs in query_shape_hash_stability.yml). The queryShapeHash should also match on mongos and on mongod.
One potential way to do this would be to parse the original update request, and then modify the update with timeseries rewrites, and then parse the update again for actual execution similar to what we currently do for views on find/agg.
- is duplicated by
-
SERVER-117999 Investigate why timeseries_hint_id.js fails in sharded_collections_query_shape_hash_stability suite
-
- Closed
-
-
SERVER-118000 Investigate why timeseries_update_arbitrary_updates_not_enabled.js fails in sharded_collections_query_shape_hash_stability suite
-
- Closed
-
-
SERVER-118551 Investigate why timeseries_insert_after_update.js fails in sharded_collections_query_shape_hash_stability suite
-
- Closed
-
- is related to
-
SERVER-119281 Skip recording timeseries updates
-
- In Progress
-