Hi all! My team is laboring between the decision to fully commit to zero-downtime schema change operations resulting in needing to fully reindex the new collection and then point the alias to it, and allowing acceptable write-blocking schema changes. Is there information somewhere about "how long" an operation like "adding a new field" or "deleting a field" against a collection with data in it would take, ie how long write operations would be blocked for? I think this is a crux that will help us decide. Thank you!

There's unfortunately no one answer to that question, because it completely depends on the shape of your data, and the number of documents in your collection

Is there no rough "napkin" math approach I could take? I'm even look for ridiculous lower/upper bounds.

I've seen some changes on collections with a 10s of thousands of docs take about 30s and on the other hand, I've seen collections with millions of docs and several fields take a few hours

Excellent 🙏 Thank you!

Collection aliases work really smoothly for us, 1MM docs with a quite diverse and large collection schema, and TS staying very responsive throughout the indexing of the new collection/alias switch/cleanup of old collection.

Awesome, ty!!!