Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional index restore function #69

Closed
jrse opened this issue Aug 18, 2017 · 2 comments
Closed

Additional index restore function #69

jrse opened this issue Aug 18, 2017 · 2 comments

Comments

@jrse
Copy link
Contributor

jrse commented Aug 18, 2017

Currently, index restore function determine all mails belonging to a mailbox via oldindex.mailboxGUID and xattr.mailbox_guid value.
For each found rados mail object the xattr.UID is read and a lockup with the uid is done in index.log and index.backup, if found entry is used to restore the index entry.

There are several other restore functions thinkable without using old index files to restore the mailbox index. E.g. by only using XAttr.

Task is to examine if it makes sense to implement alternative restore function. And if so, what additional information needs to be saved as xattr.

@jrse
Copy link
Contributor Author

jrse commented Oct 27, 2017

The current index rebuild function uses, additionally to the already available Metadata like oid, guid, data from if existent the old index file. Namely those are mail flags and keywords. Additionally, the current rebuild tries to restore the mail_cache from the old cache. For that it uses the old sequence number of the mail, which it currently tries to restore based on uid. To be able to restore the cache also, we would need to create and update a new Metadata attribute old_sequence.

@jrse
Copy link
Contributor Author

jrse commented Oct 27, 2017

We discussed the issue and came to the conclusion, that we should make it possible for the admin to configure which "optional" mail metadata should be saved and updated in rados.
For that a new issue will be created.

@jrse jrse closed this as completed Oct 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants