iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix remaining typos 

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
This commit is contained in:
Naarcha-AWS 2022-02-04 12:02:11 -06:00
parent 406db04cc2
commit d5ef881c56
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_opensearch/rest-api/ingest-apis/create-update-ingest.md
View File

@ -57,8 +57,8 @@ Field | Type | Description
Parameter | Type | Description
:--- | :--- | :---
master_timeout | time | Explicit operation timeout for connection to master node
timeout | time | Explicit operation timeout
master_timeout | time | How long to wait for a connection to the master node.
timeout | time | How long to wait for the request to return.
## Response

2
_opensearch/rest-api/ingest-apis/index.md
View File

@ -12,4 +12,4 @@ redirect_from:
Before you index your data, OpenSearch's ingest APIs help transform your data through the creation of ingest pipelines. Pipelines are made up of processors, a customizable task that run in the order they appear in the request body. The transformed data appears in your data stream or index after each of the processors completes.
Ingest pipelines in OpenSearch are managed using ingest API operations. In production environments, your cluster should contain at least one node with the `node.roles: [ingest]`. For more information on setting up node roles within a cluster, see [Cluster Formation]({{site.url}}{{site.baseurl}}/cluster/).
Ingest pipelines in OpenSearch are managed using ingest API operations. In production environments, your cluster should contain at least one node with the node roles permission set to `ingest`. For more information on setting up node roles within a cluster, see [Cluster Formation]({{site.url}}{{site.baseurl}}/cluster/).

4
_opensearch/rest-api/ingest-apis/simulate-ingest.md
View File

@ -60,8 +60,8 @@ verbose | boolean | Verbose mode. Display data output for each processor in exec
Field | Type | Description
:--- | :--- | :---
`pipeline` | object | The pipeline you want to simulate. When included without the pipeline `{id}` inside the request path, the response simulates the last pipeline created
`docs` | array of objects | The documents you want to use to test the pipeline
`pipeline` | object | The pipeline you want to simulate. When included without the pipeline `{id}` inside the request path, the response simulates the last pipeline created.
`docs` | array of objects | The documents you want to use to test the pipeline.
The `docs` field can include the following subfields: