[SERVER-75819] Do not use default value for missing fields when comparing time-series options Created: 07/Apr/23  Updated: 26/Oct/23

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

Type: Bug Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: former-storex-namer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-76411 Set missing time-series options field... Backlog
depends on SERVER-75818 Fix time-series options when sharding... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Sprint: Execution Team 2023-05-01, Execution Team 2023-05-15, Execution Team 2023-05-29, Execution Team 2023-06-12, Execution NAMR Team 2023-06-26
Participants:

 Description   

When comparing two time-series options in optionsAreEqual(), we generate the correct values for some missing fields like`bucketMaxSpanSeconds`. This will consider two options like {granularity: "seconds", bucketMaxSpanSeconds: 3600}, {} equal. 


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