[SERVER-29496] validate should work on a database as well as a collection Created: 07/Jun/17  Updated: 06/Dec/22  Resolved: 20/May/20

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

Type: Improvement Priority: Major - P3
Reporter: Geert Bosch Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

The reasons for this are twofold:

  • Avoids the need to do a loop in the client (see validate hook in resmoke)
  • Provides a good spot to do structural validation when grouping collections


 Comments   
Comment by Geert Bosch [ 20/May/20 ]

As we're not doing Grouped Collections, there is no reason for validate to work on databases.

Comment by Michael Cahill (Inactive) [ 14/Jun/17 ]

ian.whalen, I've discussed with geert.bosch, this seems like a reasonable approach. I don't yet have a good sense of whether this is reasonable to do in 3.6 as part of the existing epic – I've asked for it to be covered in WRITING-2019.

Comment by Ian Whalen (Inactive) [ 09/Jun/17 ]

michael.cahill here's one workaround to the problem of collection validate when GroupCollection is enabled. Trying to prioritize this for 3.5.x or not. What are your thoughts?

Generated at Thu Feb 08 04:21:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.