-
Notifications
You must be signed in to change notification settings - Fork 34
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
docs: Issue on page Specification #4009
Comments
Thanks for reporting! |
|
Previously all run/task properties of post-restore repair progress were taken directly from the restore progress. This included things like start/end time, properties, status, cause and others. It resulted in misleading progress display. This commit fixes that by deliberately leaving out, inheriting, or setting interesting repair progress fields. Fixes #4009
Previously all run/task properties of post-restore repair progress were taken directly from the restore progress. This included things like start/end time, properties, status, cause and others. It resulted in misleading progress display. This commit fixes that by deliberately leaving out, inheriting, or setting interesting repair progress fields. Fixes #4009
Previously all run/task properties of post-restore repair progress were taken directly from the restore progress. This included things like start/end time, properties, status, cause and others. It resulted in misleading progress display. This commit fixes that by deliberately leaving out, inheriting, or setting interesting repair progress fields. Fixes #4009
I would like to report an issue on page https://manager.docs.scylladb.com/branch-3.3/backup/specification
Problem
meta
,schema
andsst
exact directory structure is not clear.It seems that the path for schema is incorrect (no
schema
directory):meta/cluster/<cluster ID>/task_<task ID>_tag_<snapshot tag>_schema_with_internals.json.gz
Suggest a fix
Make both the line and the drawing of the directories explicitly start from root (
/
).e.g:
/meta/schema/cluster/<cluster ID>/task_<task ID>_tag_<snapshot tag>_schema_with_internals.json.gz
The text was updated successfully, but these errors were encountered: