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
..
index_actor.rs	use write sender for updates	2021-03-18 08:32:05 +01:00
mod.rs	change payload send to use stream methods	2021-03-22 19:49:21 +01:00
update_actor.rs	add json payload check on document addition	2021-03-16 14:28:13 +01:00
update_handler.rs	last review edits + fmt	2021-03-15 18:11:10 +01:00
update_store.rs	last review edits + fmt	2021-03-15 18:11:10 +01:00
updates.rs	last review edits + fmt	2021-03-15 18:11:10 +01:00
uuid_resolver.rs	create uuid on successful update addition	2021-03-18 09:09:26 +01:00