[SERVER-37839] Identify in-progress index builds as building in the index specs that the listIndexes command returns Created: 30/Oct/18  Updated: 29/Oct/23  Resolved: 07/Nov/18

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

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

Issue Links:
Related
related to SERVER-47842 [4.4] listIndexes with includeBuildUU... Closed
related to SERVER-37721 Add a command argument to listIndexes... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-11-05, Storage NYC 2018-11-19
Participants:

 Description   

SERVER-37721 optionally includes in-progress index builds in listIndexes results, but the returned index specs do not reflect the difference between in-progress and ready indexes. We must be able to tell the difference, for the purposes expressed in SERVER-37721.

This is as simple as exposing

{ready:false}

and

{ready:true}

in the index specs that listIndexes returns.

Note: if I recall right, we currently interpret the absence of the 'ready' field in the persisted index catalog entry as either true or false – we don't persist it all the time. I think the higher level parsing code interprets it correctly for the in-memory index catalog at least: extend the interpretation to listIndexes results.



 Comments   
Comment by Githook User [ 07/Nov/18 ]

Author:

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

Message: SERVER-37839 listIndexes adds indexBuildUUID field to in-progress index specs
Branch: master
https://github.com/mongodb/mongo/commit/40d866bd0829e6548341e347ee5f5b4a2a73c388

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