prepare_commit()is a bit risky from a user point of view because you need to be really careful of what's happening between
prepared_commit.commit(). So why not calling commit immediately instead of encouraging the user to use this API.
commit_with_payload(payload)that would not break the current API.
And another question (sorry, I hope I'm not spamming this channel too much...)
I'm using tantivy in a notion-like app, and I'd like to index new user input as quick as possible. However, I don't want to make POST operations slow by depending on the
commit action, which can take a couple of seconds. So I run this async in an actix Actor, which makes it a bit better. However, If many users are posting a lot of changes, the Actor commits multiple times per second, which is probably far too much. So I've added a timer, which prevents a commit from happening too often, but I think I should use a throttle instead of this mechanic...
Anyway, I was wondering what others used for this!