[SERVER-54819] Consolidate null and missing time-series metadata, or always distinguish Created: 26/Feb/21  Updated: 06/Dec/22  Resolved: 29/Mar/21

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Optimization
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-55213 Distinguish between null and missing ... Closed
duplicates SERVER-55061 Materialize literal null metadata in ... Closed
Assigned Teams:
Query Optimization
Operating System: ALL
Participants:

 Description   

An ambiguity arose while implementing SERVER-53484. It seems that today we are not consistent with treating null as null or missing as null within a time-series collection's metadata fields.

This ticket tracks the work to ensure we have consistent behavior and that our rewrite optimizations are correct in the face of nullish metadata being unpacked in $_internalUnpackBucket.


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