[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: |
|
||||||||||||||||
| 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: |