From 73b143a8c50a2cea97246b8b2a30a4c680843957 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 2 Apr 2024 16:26:26 +0000 Subject: [PATCH] feat: index param in async search (#6816) * feat: index param in async search Signed-off-by: Ian Menendez * feat: requested changes Signed-off-by: Ian Menendez --------- Signed-off-by: Ian Menendez Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> (cherry picked from commit 9f35e939cbf179047d1289a18959ee47c95c4c64) Signed-off-by: github-actions[bot] --- _search-plugins/async/index.md | 1 + _security/access-control/users-roles.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/_search-plugins/async/index.md b/_search-plugins/async/index.md index a663e7faf9..099279ba91 100644 --- a/_search-plugins/async/index.md +++ b/_search-plugins/async/index.md @@ -31,6 +31,7 @@ Options | Description | Default value | Required `wait_for_completion_timeout` | The amount of time that you plan to wait for the results. You can see whatever results you get within this time just like in a normal search. You can poll the remaining results based on an ID. The maximum value is 300 seconds. | 1 second | No `keep_on_completion` | Whether you want to save the results in the cluster after the search is complete. You can examine the stored results at a later time. | `false` | No `keep_alive` | The amount of time that the result is saved in the cluster. For example, `2d` means that the results are stored in the cluster for 48 hours. The saved search results are deleted after this period or if the search is canceled. Note that this includes the query execution time. If the query overruns this time, the process cancels this query automatically. | 12 hours | No +`index` | The name of the index to be searched. Can be an individual name, a comma-separated list of indexes, or a wildcard expression of index names. | All indexes in the cluster | No #### Example request diff --git a/_security/access-control/users-roles.md b/_security/access-control/users-roles.md index ae7670bc29..687796d0c4 100644 --- a/_security/access-control/users-roles.md +++ b/_security/access-control/users-roles.md @@ -29,7 +29,7 @@ OpenSearch Dashboards provides a user-friendly interface for managing roles. Rol ### Editing the `roles.yml` file If you want more granular control of your security configuration, you can edit roles and their associated permissions in the `roles.yml` file. This method provides direct access to the underlying configuration and can be version controlled for use in collaborative development environments. -For more information about creating roles, see the [Create roles][https://opensearch.org/docs/latest/security/access-control/users-roles/#create-roles) documentation. +For more information about creating roles, see the [Create roles](https://opensearch.org/docs/latest/security/access-control/users-roles/#create-roles) documentation. Unless you need to create new [reserved or hidden users]({{site.url}}{{site.baseurl}}/security/access-control/api/#reserved-and-hidden-resources), we **highly** recommend using OpenSearch Dashboards or the REST API to create new users, roles, and role mappings. The `.yml` files are for initial setup, not ongoing use. {: .warning }