generated from amazon-archives/__template_Custom
-
Notifications
You must be signed in to change notification settings - Fork 35
[CCI] Create advanced index actions guide #147
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
Merged
Xtansia
merged 9 commits into
opensearch-project:main
from
Nicksqain:advanced-index-actions-rs-guide
Apr 24, 2023
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
776d31a
Create advanced index actions guide
Nicksqain 752799a
Create advanced index lifecycle guide
Nicksqain 044fafd
Update advanced index actions guide to correct commit
Nicksqain dfd6cf7
Add link to guides
Nicksqain 9519a0d
Cargo formatting
Nicksqain de375bb
Set client instance to consistent with other guides
Nicksqain 6ff32af
Correcting tabulation and text errors
Nicksqain 2315a1e
Correcting USER_GUIDE.md
Nicksqain 70b587d
Correcting USER_GUIDE.md
Nicksqain File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,103 @@ | ||
| # Advanced Index Actions | ||
|
|
||
| In this guide, we will look at some advanced index actions that are not covered in the [Index Lifecycle](index_lifecycle.md) guide. | ||
|
|
||
| ## Setup | ||
|
|
||
| Let's create a client instance, and an index named `movies`: | ||
|
|
||
| ```ruby | ||
| require 'opensearch-ruby' | ||
| client = OpenSearch::Client.new( | ||
| host: 'https://admin:admin@localhost:9200', | ||
| transport_options: { ssl: { verify: false } }) | ||
| client.indices.create(index: :movies) | ||
| ``` | ||
|
|
||
| ## API Actions | ||
|
|
||
| ### Clear index cache | ||
|
|
||
| You can clear the cache of an index or indices by using the `indices.clear_cache` API action. The following example clears the cache of the `movies` index: | ||
|
|
||
| ```ruby | ||
| client.indices.clear_cache(index: :movies) | ||
| ``` | ||
|
|
||
| By default, the `indices.clear_cache` API action clears all types of cache. To clear specific types of cache pass the the `query`, `fielddata`, or `request` parameter to the API action: | ||
|
|
||
| ```ruby | ||
| client.indices.clear_cache(index: :movies, query: true) | ||
| client.indices.clear_cache(index: :movies, fielddata: true, request: true) | ||
| ``` | ||
|
|
||
| ### Flush index | ||
|
|
||
| Sometimes you might want to flush an index or indices to make sure that all data in the transaction log is persisted to the index. To flush an index or indices use the `indices.flush` API action. The following example flushes the `movies` index: | ||
|
|
||
| ```ruby | ||
| client.indices.flush(index: :movies) | ||
| ``` | ||
|
|
||
| ### Refresh index | ||
|
|
||
| You can refresh an index or indices to make sure that all changes are available for search. To refresh an index or indices use the `indices.refresh` API action: | ||
|
|
||
| ```ruby | ||
| client.indices.refresh(index: :movies) | ||
| ``` | ||
|
|
||
| ### Open/Close index | ||
|
|
||
| You can close an index to prevent read and write operations on the index. A closed index does not have to maintain certain data structures that an opened index require, reducing the memory and disk space required by the index. The following example closes and reopens the `movies` index: | ||
|
|
||
| ```ruby | ||
| client.indices.close(index: :movies) | ||
| client.indices.open(index: :movies) | ||
| ``` | ||
|
|
||
| ### Force merge index | ||
|
|
||
| You can force merge an index or indices to reduce the number of segments in the index. This can be useful if you have a large number of small segments in the index. Merging segments reduces the memory footprint of the index. Do note that this action is resource intensive and it is only recommended for read-only indices. The following example force merges the `movies` index: | ||
|
|
||
| ```ruby | ||
| client.indices.forcemerge(index: :movies) | ||
| ``` | ||
|
|
||
| ### Clone index | ||
|
|
||
| You can clone an index to create a new index with the same mappings, data, and MOST of the settings. The source index must be in read-only state for cloning. The following example blocks write operations from `movies` index, clones the said index to create a new index named `movies_clone`, then re-enables write: | ||
|
|
||
| ```ruby | ||
| client.indices.add_block(index: :movies, block: :write) | ||
| client.indices.clone(index: :movies, target: :movies_clone) | ||
| client.indices.put_settings(index: :movies, body: { index: { blocks: { write: false } } }) | ||
| ``` | ||
|
|
||
| ### Split index | ||
|
|
||
| You can split an index into another index with more primary shards. The source index must be in read-only state for splitting. The following example create the read-only `books` index with 30 routing shards and 5 shards (which is divisible by 30), splits index into `bigger_books` with 10 shards (which is also divisible by 30), then re-enables write: | ||
Nicksqain marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ```ruby | ||
| client.indices.create( | ||
| index: :books, | ||
| body: { settings: { | ||
| index: { number_of_shards: 5, | ||
| number_of_routing_shards: 30, | ||
| blocks: { write: true } } } }) | ||
|
|
||
| client.indices.split( | ||
| index: :books, | ||
| target: :bigger_books, | ||
| body: { settings: { index: { number_of_shards: 10 } } }) | ||
|
|
||
| client.indices.put_settings(index: :books, body: { index: { blocks: { write: false } } }) | ||
| ``` | ||
|
|
||
| ## Cleanup | ||
|
|
||
| Let's delete all the indices we created in this guide: | ||
|
|
||
| ```ruby | ||
| client.indices.delete(index: %i[movies books movies_clone bigger_books]) | ||
| ``` | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That file doesn't exist yet, so the link checker breaks. You can combine all the guides in 1 PR or make them in order they link to each-other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dblock Can we wait for the index lifecycle to merge first and then re-run the link checker?