-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Automatic snapshot naming #7939
Comments
I would be wary of just having an incrementing number as it doesn't containing any information about the point in time the snapshot relates to, but maybe we could use something like the combination of timestamp and flake ID so that the timestamp indicates the point in time the snapshot was created and the flake ID makes the name unique? |
@colings86 the snapshot metadata already includes the timestamp, so it's not necessary for preserving snapshot creation time. Still, I support using the timestamp as id because timestamps are useful when looking at a list of snapshot names. Most of our snapshots are named with the pattern |
We looked at this today with @ywelsch and we came up with the idea of reusing the date math expression resolver that already exists for indices. This way we could create a snapshot like
and it would be resolved to |
move test case to DedicatedClusterSnapshotRestoreIT
extended doc: example is added. referring to indices date math more clearly
…bad-mkay * elastic/6.x: [ML] Wait for ML indices in rolling upgrade tests (elastic#30615) Watcher: Ensure secrets integration tests also run triggered watch (elastic#30478) Move allocation awareness attributes to list setting (elastic#30626) [Docs] Update code snippet in has-child-query.asciidoc (elastic#30510) Allow date math for naming newly-created snapshots (elastic#7939) (elastic#30479) Awaits fix a failing test Switch many QA projects to use new style requests (elastic#30574) QA: System property to override distribution (elastic#30591)
It would be useful if Elasticsearch could generate automatic snapshot names. This would be a POST to the repository instead of a PUT to a snapshot name.
The name could be generated by incrementing a number (
1
,2
,3
, etc), getting the current timestamp, or generating a flake id.To organize snapshots in a repository, the POST action could accept a prefix parameter.
The text was updated successfully, but these errors were encountered: