[RemoteStore]: Provide support for Composite repository to support SSE encryption #19528
+930
−108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As part of this PR we are adding support for Composite repository for the remote store SSE enabled Index data for Segment/Translog.
Currently Remote-store creates a single repository to store Segment/Translog data. To support sse enabled repository we will need to provide support for composite repository which will be created based on presence of
sse_enabled
flag. The repository created will have specific encryption type to support "SSE" feature. These will be Internal repository matching the existing repository "Translog/Segment" suffixed with "-sse" to the existing repo name.Related Issues
Resolves #[https://github.com/https://github.com//issues/19235]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.