From f2187da0686d2e7fb6491146ce7dee80008a0a23 Mon Sep 17 00:00:00 2001 From: Caroline <113052567+carolxob@users.noreply.github.com> Date: Tue, 25 Oct 2022 10:34:36 -0600 Subject: [PATCH] Added second paragraph to Stack traces option (#1403) * Added second paragraph to Stack traces option Signed-off-by: carolxob * Update _opensearch/common-parameters.md Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update _opensearch/common-parameters.md * Update common-parameters.md Signed-off-by: carolxob Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --- _opensearch/common-parameters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_opensearch/common-parameters.md b/_opensearch/common-parameters.md index aee474ec..2fd8b335 100644 --- a/_opensearch/common-parameters.md +++ b/_opensearch/common-parameters.md @@ -14,4 +14,4 @@ Human-readable output | To convert output units to human-readable values (for ex Pretty result | To get back JSON responses in a readable format, add `?pretty=true` to the request URL. | `GET /_search?pretty=true` Content type | To specify the type of content in the request body, use the `Content-Type` key name in the request header. Most operations support JSON, YAML, and CBOR formats. | `POST _scripts/ -H 'Content-Type: application/json` Request body in query string | If the client library does not accept a request body for non-POST requests, use the `source` query string parameter to pass the request body. Also, specify the `source_content_type` parameter with a supported media type such as `application/json`. | `GET _search?source_content_type=application/json&source={"query":{"match_all":{}}}` -Stack traces | To include the error stack trace in the response when an exception is raised, add `error_trace=true` to the request URL. | `GET /_search?error_trace=true` +Stack traces | To include the error stack trace in the response when an exception is raised, add `error_trace=true` to the request URL.

When the configuration setting `http.detailed_errors.enabled` is set to `false` in opensearch.yml, `error_trace=true` will not contain a detailed error message.| `GET /_search?error_trace=true`