You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
Currently Conversations are deleted from the Repository. Because of this CloudSync does not work as this is based on the modified date of conversation.
Because of that Conversation are only deleted from the embedded SolrIndex on that host that performs the delete operation and stay in indexes of others.
This causes the SolrIndex to be out-of-sync with the state in the Repository.
To avoid this problems Conversations MUST NOT deleted from the repository but need to be marked as deleted as part of the deletion some/most of the information for those conversations can however be removed from the repository (e.g. all messages)
The text was updated successfully, but these errors were encountered:
I used an ssh tunnel to a mongoDB running on a different host (ssh user@host -L 27017:127.0.0.1:27017)
Doing so simulates a cloud like setting wehre multiple Smarti instances do use the same MongoDB. The Smarti instance on host needs to use the cloud-sync feature to detect deletions you perform on the smarti instance on your localhost
this test by @westei is a developers test and I believe it’s been performed with highest expertise available => let’s merge this and verify on our test environment
Currently Conversations are deleted from the Repository. Because of this CloudSync does not work as this is based on the modified date of conversation.
Because of that Conversation are only deleted from the embedded SolrIndex on that host that performs the delete operation and stay in indexes of others.
This causes the SolrIndex to be out-of-sync with the state in the Repository.
To avoid this problems Conversations MUST NOT deleted from the repository but need to be marked as deleted as part of the deletion some/most of the information for those conversations can however be removed from the repository (e.g. all messages)
The text was updated successfully, but these errors were encountered: