Go to file
bors[bot] 868658f3d8
Merge #109
109: Make updates atomic r=curquiza a=MarinPostma

Until now, the index_uid->uuid mapping was done before the update was written to disk in the case of automatic index creation. This was an issue when the update failed, and the index would still exists in the uuid resolver.

This is fixed by this pr, by first creating the update with an uuid if the index does not exist, and then register this uuid to the uuid resolver.

This is preliminary work to the implementation of snapshots (#19).

This pr also changes the `resolve` method on the `UuidResolver` to `get` to make it clearer.


The `create_uuid` method may be bound to disappear when the index name resolution is handled by a remote machine.

Co-authored-by: mpostma <postma.marin@protonmail.com>
2021-03-24 12:24:32 +00:00
.github Update release-draft-template.yml 2021-03-16 15:16:33 +01:00
meilisearch-error last review edits + fmt 2021-03-15 18:11:10 +01:00
meilisearch-http Merge #109 2021-03-24 12:24:32 +00:00
.dockerignore update relevant changes from master 2021-03-10 14:43:10 +01:00
.gitignore restructure project 2021-03-10 13:46:49 +01:00
bors.toml Add bors configuration 2021-03-16 13:08:26 +01:00
Cargo.lock create uuid on successful update addition 2021-03-18 09:09:26 +01:00
Cargo.toml restructure project 2021-03-10 13:46:49 +01:00
Dockerfile restructure project 2021-03-10 13:46:49 +01:00
LICENSE update relevant changes from master 2021-03-10 14:43:10 +01:00
README.md initial commit 2020-12-12 13:32:06 +01:00

transplant of meilisearch http on the new engine