spacing

_opensearch/rest-api/create-index.md

@@ -1,9 +1,8 @@
 ---
 layout: default
 title: Create index
-parent: Index APIs
-grand_parent: REST API reference
-nav_order: 1
+parent: REST API reference
+nav_order: 3
 ---
 
 # Create index

_opensearch/rest-api/index-apis/delete-index.md

@@ -1,45 +0,0 @@
----
-layout: default
-title: Delete index
-parent: Index APIs
-grand_parent: REST API reference
-nav_order: 5
----
-
-# Delete index
-Introduced 1.0
-{: .label .label-purple }
-
-If you no longer need an index, you can use the delete index API operation to delete it.
-
-## Example
-
-```json
-DELETE /sample-index
-```
-
-## Path and HTTP methods
-
-```
-DELETE /<index-name>
-```
-
-## URL parameters
-
-All parameters are optional.
-
-Parameter | Type | Description
-:--- | :--- | :---
-allow_no_indices | Boolean | Whether to ignore wildcards that don't match any indices. Default is true.
-expand_wildcards | String | Expands wildcard expressions to different indices. Combine multiple values with commas. Available values are all (match all indices), open (match open indices), closed (match closed indices), hidden (match hidden indices), and none (do not accept wildcard expressions), which must be used with open, closed, or both. Default is open.
-ignore_unavailable | Boolean | If true, OpenSearch does not include missing or closed indices in the response.
-master_timeout | Time | How long to wait for a connection to the master node. Default is `30s`.
-timeout | Time | How long to wait for the response to return. Default is `30s`.
-
-
-## Response
-```json
-{
-  "acknowledged": true
-}
-```

_opensearch/rest-api/index-apis/get-index.md

@@ -1,76 +0,0 @@
----
-layout: default
-title: Get index
-parent: Index APIs
-grand_parent: REST API reference
-nav_order: 10
----
-
-# Get index
-Introduced 1.0
-{: .label .label-purple }
-
-You can use the get index API operation to return information about an index.
-
-## Example
-
-```json
-GET /sample-index
-```
-
-## Path and HTTP methods
-
-```
-GET /<index-name>
-```
-
-## URL parameters
-
-All parameters are optional.
-
-Parameter | Type | Description
-:--- | :--- | :---
-allow_no_indices | Boolean | Whether to ignore wildcards that don't match any indices. Default is true.
-expand_wildcards | String | Expands wildcard expressions to different indices. Combine multiple values with commas. Available values are all (match all indices), open (match open indices), closed (match closed indices), hidden (match hidden indices), and none (do not accept wildcard expressions), which must be used with open, closed, or both. Default is open.
-flat_settings | Boolean | Whether to return settings in the flat form, which can improve readability, especially for heavily nested settings. For example, the flat form of "index": { "creation_date": "123456789" } is "index.creation_date": "123456789".
-include_defaults | Boolean | Whether to include default settings as part of the response. This parameter is useful for identifying the names and current values of settings you want to update.
-ignore_unavailable | Boolean | If true, OpenSearch does not include missing or closed indices in the response.
-local | Boolean | Whether to return information from only the local node instead of from the master node. Default is false.
-master_timeout | Time | How long to wait for a connection to the master node. Default is `30s`.
-
-
-## Response
-```json
-{
-  "sample-index1": {
-    "aliases": {},
-    "mappings": {},
-    "settings": {
-      "index": {
-        "creation_date": "1633044652108",
-        "number_of_shards": "2",
-        "number_of_replicas": "1",
-        "uuid": "XcXA0aZ5S0aiqx3i1Ce95w",
-        "version": {
-          "created": "135217827"
-        },
-        "provided_name": "sample-index1"
-      }
-    }
-  }
-}
-```
-
-## Response body fields
-
-Field | Description
-:--- | :---
-aliases | Any aliases associated with the index.
-mappings | Any mappings in the index.
-settings | The index's settings
-creation_date | The Unix epoch time of when the index was created.
-number_of_shards | How many shards the index has.
-number_of_replicas | How many replicas the index has.
-uuid | The index's uuid.
-created | The version of OpenSearch when the index was created.
-provided_name | Name of the index.

_opensearch/rest-api/index-apis/index.md

@@ -1,16 +0,0 @@
----
-layout: default
-title: Index APIs
-parent: REST API reference
-has_children: true
-nav_order: 3
-redirect_from:
-  - /opensearch/rest-api/index-apis/
----
-
-# Index APIs
-
-The index API operations let you interact with indices in your cluster. Using these operations, you can create, delete, close, and complete other index-related operations.
-
-If you use the security plugin, make sure you have the appropriate permissions.
-{: .note }

_opensearch/rest-api/update-mapping.md

@@ -6,8 +6,6 @@ nav_order: 6
 ---
 
 # Update mapping
-Introduced 1.0
-{: .label .label-purple }
 
 If you want to update an index's mappings to add or update field types after index creation, you can do so with the update mapping API operation.
 

_upgrade-to/upgrade-to.md

@@ -179,3 +179,116 @@ If you are upgrading an Open Distro for Elasticsearch cluster, we recommend firs
      }
    }
    ```
+
+## Upgrade tool
+
+The `opensearch-upgrade` tool lets you automate some of the steps in [Upgrade to OpenSearch]({{site.url}}{{site.baseurl}}/upgrade-to/upgrade-to/#upgrade-to-opensearch), eliminating the need for error-prone manual operations.
+
+The `opensearch-upgrade` tool performs the following functions:
+
+- Imports any existing configurations and applies it to the new installation of OpenSearch.
+- Installs any existing core plugins.
+
+### Limitations
+
+The `opensearch-upgrade` tool doesn't perform an end-to-end upgrade:
+
+- You need to run the tool on each node of the cluster individually as part of the upgrade process.
+- The tool doesn't provide a rollback option after you've upgraded a node, so make sure you follow best practices and take backups.
+- You must install all community plugins (if available) manually.
+- The tool only validates any keystore settings at service start-up time, so you must manually remove any unsupported settings for the service to start.
+
+### Using the upgrade tool
+
+To perform a rolling upgrade using the [OpenSearch tarball]({{site.url}}{{site.baseurl}}/opensearch/install/tar/) distribution:
+
+Check [Upgrade paths]({{site.url}}{{site.baseurl}}/upgrade-to/upgrade-to/#upgrade-paths) to make sure that the version you’re upgrading to is supported and whether you need to upgrade to a supported Elasticsearch OSS version first.
+{: .note }
+
+1. Disable shard allocation to prevent Elasticsearch OSS from replicating shards as you shut down nodes:
+
+   ```json
+   PUT _cluster/settings
+   {
+     "persistent": {
+       "cluster.routing.allocation.enable": "primaries"
+     }
+   }
+   ```
+
+1. On any one of the nodes, download and extract the OpenSearch tarball to a new directory.
+
+1. Make sure the following environment variables are set:
+
+    - `ES_HOME` - Path to the existing Elasticsearch installation home.
+
+      ```bash
+      export ES_HOME = /home/workspace/upgrade-demo/node1/elasticsearch-7.10.2
+      ```
+
+    - `ES_PATH_CONF` - Path to the existing Elasticsearch config directory.
+
+      ```bash
+      export ES_PATH_CONF = /home/workspace/upgrade-demo/node1/os-config
+      ```
+
+    - `OPENSEARCH_HOME` - Path to the OpenSearch installation home.
+
+      ```bash
+      export OPENSEARCH_HOME = /home/workspace/upgrade-demo/node1/opensearch-1.0.0
+      ```
+
+    - `OPENSEARCH_PATH_CONF` - Path to the OpenSearch config directory.
+
+      ```bash
+      export OPENSEARCH_PATH_CONF = /home/workspace/upgrade-demo/node1/opensearch-config
+      ```
+
+1. The `opensearch-upgrade` tool is in the `bin` directory of the distribution. Run the following command from the distribution home:
+
+   Make sure you run this tool as the same user running the current Elasticsearch service.
+   {: .note }
+
+   ```json
+   ./bin/opensearch-upgrade
+   ```
+
+1. Stop Elasticsearch OSS on the node.
+
+   On Linux distributions that use systemd, use this command:
+
+   ```bash
+   sudo systemctl stop elasticsearch.service
+   ```
+
+   For tarball installations, find the process ID (`ps aux`) and kill it (`kill <pid>`).
+
+1. Start OpenSearch on the node:
+
+   ```json
+   ./bin/opensearch -d.
+   ```
+
+1. Repeat steps 2--6 until all nodes are using the new version.
+
+1. After all nodes are using the new version, re-enable shard allocation:
+
+   ```json
+   PUT _cluster/settings
+   {
+    "persistent": {
+       "cluster.routing.allocation.enable": "all"
+     }
+   }
+   ```
+
+### How it works
+
+Behind the scenes, the `opensearch-upgrade` tool performs the following tasks in sequence:
+
+1. Looks for a valid Elasticsearch installation on the current node. After it finds the installation, it reads the `elasticsearch.yml` file to get the endpoint details and connects to the locally running Elasticsearch service. If the tool can't find an Elasticsearch installation, it tries to get the path from the `ES_HOME` location.
+1. Verifies if the existing version of Elasticsearch is compatible with the OpenSearch version. It prints a summary of the information gathered to the console and prompts you for a confirmation to proceed.
+1. Imports the settings from the `elasticsearch.yml` config file into the `opensearch.yml` config file.
+1. Copies across any custom JVM options from the `$ES_PATH_CONF/jvm.options.d` directory into the `$OPENSEARCH_PATH_CONF/jvm.options.d` directory. Similarly, it also imports the logging configurations from the `$ES_PATH_CONF/log4j2.properties` file into the `$OPENSEARCH_PATH_CONF/log4j2.properties` file.
+1. Installs the core plugins that you’ve currently installed in the `$ES_HOME/plugins` directory. You must install all other third-party community plugins manually.
+1. Imports the secure settings from the `elasticsearch.keystore` file (if any) into the `opensearch.keystore` file. If the keystore file is password protected, the `opensearch-upgrade` tool prompts you to enter the password.