-
Notifications
You must be signed in to change notification settings - Fork 617
Create documentation for snapshots with hashed prefix path type #8196
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
Changes from 2 commits
f18a5e3
656459a
ce762a0
2d5e231
6e97500
5e9e2aa
5e7ca66
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,6 +43,14 @@ | |
Request field | Description | ||
:--- | :--- | ||
`prefix_mode_verification` | When enabled, adds a hashed value of a random seed to the prefix for repository verification. For remote-store-enabled clusters, you can add the `setting.prefix_mode_verification` setting to the node attributes for the supplied repository. This field works with both new and existing repositories. Optional. | ||
`shard_path_type` | This setting is used to control the path stucture of shard level blobs. Defaults to fixed. There are 2 other possible values - 1. `hashed_prefix` 2. `hashed_infix`. More details are shared below. Optional. | ||
Check failure on line 46 in _api-reference/snapshots/create-repository.md
|
||
|
||
##### shard_path_type values | ||
Check failure on line 48 in _api-reference/snapshots/create-repository.md
|
||
1. FIXED - This keep the path structure in the existing hierarchical manner. eg - `<ROOT>/<BASE_PATH>/indices/<index-id>/0/<SHARD_BLOBS>` | ||
Check warning on line 49 in _api-reference/snapshots/create-repository.md
|
||
ashking94 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
2. HASHED_PREFIX - This prepends a hashed prefix at the start of path for each unique shard id. eg - `<ROOT>/<HASH-OF-INDEX-ID-AND-SHARD-ID>/<BASE_PATH>/indices/<index-id>/0/<SHARD_BLOBS>` | ||
Check warning on line 50 in _api-reference/snapshots/create-repository.md
|
||
3. HASHED_INFIX - This appends a hashed prefix after the base path for each unique shard id. eg - `<ROOT>/<BASE-PATH>/<HASH-OF-INDEX-ID-AND-SHARD-ID>/indices/<index-id>/0/<SHARD_BLOBS>` | ||
Check warning on line 51 in _api-reference/snapshots/create-repository.md
|
||
|
||
Note - The hash method used is `fnv_1a_composite_1`. It uses the FNV1a hash function and generates a custom encoded hash value that scales well with most remote store options. The FNV1a function generates 64-bit value. The custom encoding uses the most significant 6 bits to create a url-safe base64 character and the next 14 bits to create a binary string. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Line above: Same question re: |
||
### fs repository | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.