Skip to content

Conversation

@albertzaharovits
Copy link
Contributor

This commit creates a new protected method to access (write) the index.latest blob; there exists already to opposite method to read the said blob. This change permits BlobStoreRepository implementations to have a different access behavior, compared to the other blobs, for the special index.latest blob.

NB: This change might not be REQUIRED for the encrypted repository, given the latest developments #50846 (comment) , but it seems to me like a good-to-have option.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore)

@original-brownbear
Copy link
Contributor

@albertzaharovits I think we don't need to make this change in a separate PR do we? (maybe I'm missing the reason for locking this in now?)
Can't we just make it as part of the encrypted repo PR when and if we need it?

Copy link
Contributor

@original-brownbear original-brownbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comment, I don't see why we need this yet?

@albertzaharovits
Copy link
Contributor Author

Okay @original-brownbear , thanks for taking a look!
We don't need it indeed, but it looked like a useful change, closing.

@albertzaharovits albertzaharovits deleted the blob-store-write-index-latest branch March 6, 2020 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants