Clémentine

Hey 🙂 I am not sure to understand the aim of this project. Is it supposed to make updates to MeiliSearch / Algolia index and waiting for the indexation /...

Hello @nicolasvienot! Thanks for asking. Checked with @gmourier: - Fresh news: the current options to configure the auto batching (`--debounce-duration-sec`, `--max-batch-size` and `--max-documents-per-batch`) will be removed, so no env variable...

What we expect one day (for v1 probably) is the autobatching feature to be totally transparent: nothing to configure, it works by default and you cannot disable it If, for...

FYI, I've just created the related spec: https://github.com/meilisearch/specifications/pull/162 I've just added it to this issue description.

FYI, the `batchUid` fields has been removed, see this issue: https://github.com/meilisearch/meilisearch/issues/2676

Hello everyone watching this issue! We have just released [v0.29.0rc1](https://github.com/meilisearch/meilisearch/releases/tag/v0.29.0rc1), which is a release candidate of v0.29.0 🔥 It means you can test the auto-batching working by default in this...

Hello @finalgamer Yes, it will impact any document update, partial or not 😄 I've updated the issue to make it clearer!

The spec is available here: https://github.com/meilisearch/specifications/pull/168

Some clarification following questions I got internally - When doing a dump: soft-deleted documents are not included, so if you import the dump, the soft-deleted documents will not be present...

Until we don't detail how it works exactly since we can break it at every moment, I'm not against this decision. People know what "soft-deletion" is since it's really common.