Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion pipeline/outputs/elasticsearch.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,6 +230,7 @@ If you see `action_request_validation_exception` errors on your pipeline with Fl
Elastic Cloud is now on version 8 so the type option must be removed by setting `Suppress_Type_Name On` as indicated above.

Without this you will see errors like:
```

```text
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"}],"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"},"status":400}
```
10 changes: 10 additions & 0 deletions pipeline/outputs/opensearch.md
Original file line number Diff line number Diff line change
Expand Up @@ -146,3 +146,13 @@ Example configuration:
```

Notice that the `Port` is set to `443`, `tls` is enabled, and `AWS_Region` is set.

### Action/metadata contains an unknown parameter type

Similarly to Elastic Cloud, OpenSearch in version 2.0 and above needs to have type option being removed by setting `Suppress_Type_Name On`.

Without this you will see errors like:

```text
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"}],"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"},"status":400}
```