[SERVER-55061] Materialize literal null metadata in measurements when it is null in buckets collection Created: 09/Mar/21  Updated: 29/Oct/23  Resolved: 18/Mar/21

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 5.0 Required
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Eric Cox (Inactive) Assignee: Yoon Soo Kim
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-55213 Distinguish between null and missing ... Closed
Duplicate
is duplicated by SERVER-54819 Consolidate null and missing time-ser... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-03-22
Participants:

 Description   

The bucket format encodes missing and null metadata sections as null. The current getNext() implementation in the BucketUnpacker drops the metadata field if it's null. We should relax this behavior and produce metadata values if the bucket has a metadata region, otherwise we should continue to drop it if it doesn't exist.



 Comments   
Comment by Githook User [ 18/Mar/21 ]

Author:

{'name': 'Yoonsoo Kim', 'email': 'yoonsoo.kim@mongodb.com', 'username': 'yun-soo'}

Message: SERVER-55061 Handle missing meta and null meta differently
Branch: master
https://github.com/mongodb/mongo/commit/a97223f6f28f150eede362227db8b36048beeec4

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