[SERVER-52529] define validator for buckets in a time-series collection Created: 31/Oct/20  Updated: 29/Oct/23  Resolved: 23/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-11-30
Participants:

 Description   

Set the validator option to a JSON schema enforcing constraints on bucket documents. This validation is only structural to prevent accidental corruption by users and cannot cover all constraints. Updates by mongod itself are valid by construction, so don't require validation. Leave the validationLevel and validationAction to their strict/error defaults. Validation includes the following:
Top-level field types of the bucket. No fields other than those defined below.
Field types of fields inside control as defined below. Field type of control.time



 Comments   
Comment by Githook User [ 21/Nov/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-52529 enable schema validation on time-series bucket collections
Branch: master
https://github.com/mongodb/mongo/commit/40fb4677db516968c8560b2e7db9c587b887d79a

Comment by Githook User [ 21/Nov/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-52529 time-series upserts should bypass document validation
Branch: master
https://github.com/mongodb/mongo/commit/65c4f3bcf915d6fe3ca6fa620fe0b5b9b0a0d405

Comment by Githook User [ 21/Nov/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-52529 add test case for schema validation on time-series bucket collection
Branch: master
https://github.com/mongodb/mongo/commit/943845d1ea81f8f99620af5aa96737bbaae37b5d

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