[SERVER-78038] Rework timeseries_lastpoint_top.js to enable $meta field validation Created: 13/Jun/23  Updated: 22/Jun/23

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

Type: Bug Priority: Minor - P4
Reporter: Peter Volk Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
Assigned Teams:
Query Optimization
Operating System: ALL
Participants:

 Description   

With SERVER-73509 the first part of this test was enabled again. Yet the last test which includes metadata fields fails during the comparison of the result sets. This is due to the fact that the output is intended to be different. A timeseries collection treats objects that only differ by field order as being equivalent meta values. Hence the comparison collection will have more values being returned compared to the timeseries collection. We only need to check on the correct plan being selected. 


Generated at Thu Feb 08 06:37:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.