sync indexes by key and drop by name

[axgiri]

Checklist:

• Tested

issue #1274

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ae080f55-1085-495e-9ee1-dc41044a334d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[axgiri]

to avoid dealing with comparing index options (which can get messy since there are quite a few fields that could differ), decided to just drop existing indexes and recreate them every time. I was also thinking about an even simpler approach, just drop all indexes at once and recreate everything. but i'm a bit worried though, could it affect app startup?

[GregJohnStewart]

@axgiri Yeah, for larger datasets I would worry about the compute impact of recreating every time, let's not drop/ recreate every time.

I think I've heard that just calling the createIndex will do nothing for existent indexes that are the same, but throw an exception for indexes that exist but are different. Would need to test to verify, but would be an easy way to know when to drop/ recreate in the exception handler there