Observed behaviour:
When you have restored a backup with the "restore-folder-method" all works fine but the elasticsearch-index
have to be rebuilded after the restore. The behaviour now is that you have the restored data but the index is the old.
When the backup was from a near date the gap isn't so big, but as an example when you migrate from an other
system to docker the index might be empty or completely different.
Expected behaviour:
Idea 1 (needed) : The documentation has to be updated that you have to reindex after restore (Even when you want this)
Idea 2 (to discuss): This can be done everytime automaticly in the restore-script that reindexes the restored data in background
Idea 3 (to discuss): There can be a restore-folder with complete reindex in parallel to "restore".. like "restore-with-reindex"
(Like the old functionality but when there is the folder ".../restore-with-reindex" the restore reindexes at the end automaticly in background)
Observed behaviour:
When you have restored a backup with the "restore-folder-method" all works fine but the elasticsearch-index
have to be rebuilded after the restore. The behaviour now is that you have the restored data but the index is the old.
When the backup was from a near date the gap isn't so big, but as an example when you migrate from an other
system to docker the index might be empty or completely different.
Expected behaviour:
Idea 1 (needed) : The documentation has to be updated that you have to reindex after restore (Even when you want this)
Idea 2 (to discuss): This can be done everytime automaticly in the restore-script that reindexes the restored data in background
Idea 3 (to discuss): There can be a restore-folder with complete reindex in parallel to "restore".. like "restore-with-reindex"
(Like the old functionality but when there is the folder ".../restore-with-reindex" the restore reindexes at the end automaticly in background)