elasticsearch-api 9.0.3 → 9.0.4

data/lib/elasticsearch/api/actions/text_structure/find_field_structure.rb

@@ -25,7 +25,7 @@ module Elasticsearch
         # Find the structure of a text field.
         # Find the structure of a text field in an Elasticsearch index.
         # This API provides a starting point for extracting further information from log messages already ingested into Elasticsearch.
-        # For example, if you have ingested data into a very simple index that has just +@timestamp+ and message fields, you can use this API to see what common structure exists in the message field.
+        # For example, if you have ingested data into a very simple index that has just `@timestamp` and message fields, you can use this API to see what common structure exists in the message field.
         # The response from the API contains:
         # * Sample messages.
         # * Statistics that reveal the most common values for all fields detected within the text and basic numeric statistics for numeric fields.
@@ -33,74 +33,85 @@ module Elasticsearch
         # * Appropriate mappings for an Elasticsearch index, which you could use to ingest the text.
         # All this information can be calculated by the structure finder with no guidance.
         # However, you can optionally override some of the decisions about the text structure by specifying one or more query parameters.
-        # If the structure finder produces unexpected results, specify the +explain+ query parameter and an explanation will appear in the response.
+        # If the structure finder produces unexpected results, specify the `explain` query parameter and an explanation will appear in the response.
         # It helps determine why the returned structure was chosen.
         #
-        # @option arguments [String] :column_names If +format+ is set to +delimited+, you can specify the column names in a comma-separated list.
+        # @option arguments [String] :column_names If `format` is set to `delimited`, you can specify the column names in a comma-separated list.
         #  If this parameter is not specified, the structure finder uses the column names from the header row of the text.
         #  If the text does not have a header row, columns are named "column1", "column2", "column3", for example.
-        # @option arguments [String] :delimiter If you have set +format+ to +delimited+, you can specify the character used to delimit the values in each row.
+        # @option arguments [String] :delimiter If you have set `format` to `delimited`, you can specify the character used to delimit the values in each row.
         #  Only a single character is supported; the delimiter cannot have multiple characters.
-        #  By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (+|+).
+        #  By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (`|`).
         #  In this default scenario, all rows must have the same number of fields for the delimited format to be detected.
         #  If you specify a delimiter, up to 10% of the rows can have a different number of columns than the first row.
         # @option arguments [Integer] :documents_to_sample The number of documents to include in the structural analysis.
         #  The minimum value is 2. Server default: 1000.
         # @option arguments [String] :ecs_compatibility The mode of compatibility with ECS compliant Grok patterns.
         #  Use this parameter to specify whether to use ECS Grok patterns instead of legacy ones when the structure finder creates a Grok pattern.
-        #  This setting primarily has an impact when a whole message Grok pattern such as +%{CATALINALOG}+ matches the input.
-        #  If the structure finder identifies a common structure but has no idea of the meaning then generic field names such as +path+, +ipaddress+, +field1+, and +field2+ are used in the +grok_pattern+ output.
+        #  This setting primarily has an impact when a whole message Grok pattern such as `%{CATALINALOG}` matches the input.
+        #  If the structure finder identifies a common structure but has no idea of the meaning then generic field names such as `path`, `ipaddress`, `field1`, and `field2` are used in the `grok_pattern` output.
         #  The intention in that situation is that a user who knows the meanings will rename the fields before using them. Server default: disabled.
-        # @option arguments [Boolean] :explain If +true+, the response includes a field named +explanation+, which is an array of strings that indicate how the structure finder produced its result.
+        # @option arguments [Boolean] :explain If `true`, the response includes a field named `explanation`, which is an array of strings that indicate how the structure finder produced its result.
         # @option arguments [String] :field The field that should be analyzed. (*Required*)
         # @option arguments [String] :format The high level structure of the text.
         #  By default, the API chooses the format.
         #  In this default scenario, all rows must have the same number of fields for a delimited format to be detected.
         #  If the format is set to delimited and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row.
-        # @option arguments [String] :grok_pattern If the format is +semi_structured_text+, you can specify a Grok pattern that is used to extract fields from every message in the text.
-        #  The name of the timestamp field in the Grok pattern must match what is specified in the +timestamp_field+ parameter.
+        # @option arguments [String] :grok_pattern If the format is `semi_structured_text`, you can specify a Grok pattern that is used to extract fields from every message in the text.
+        #  The name of the timestamp field in the Grok pattern must match what is specified in the `timestamp_field` parameter.
         #  If that parameter is not specified, the name of the timestamp field in the Grok pattern must match "timestamp".
-        #  If +grok_pattern+ is not specified, the structure finder creates a Grok pattern.
+        #  If `grok_pattern` is not specified, the structure finder creates a Grok pattern.
         # @option arguments [String] :index The name of the index that contains the analyzed field. (*Required*)
-        # @option arguments [String] :quote If the format is +delimited+, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character.
+        # @option arguments [String] :quote If the format is `delimited`, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character.
         #  Only a single character is supported.
-        #  If this parameter is not specified, the default value is a double quote (+"+).
+        #  If this parameter is not specified, the default value is a double quote (`"`).
         #  If your delimited text format does not use quoting, a workaround is to set this argument to a character that does not appear anywhere in the sample.
-        # @option arguments [Boolean] :should_trim_fields If the format is +delimited+, you can specify whether values between delimiters should have whitespace trimmed from them.
-        #  If this parameter is not specified and the delimiter is pipe (+|+), the default value is true.
-        #  Otherwise, the default value is +false+.
+        # @option arguments [Boolean] :should_trim_fields If the format is `delimited`, you can specify whether values between delimiters should have whitespace trimmed from them.
+        #  If this parameter is not specified and the delimiter is pipe (`|`), the default value is true.
+        #  Otherwise, the default value is `false`.
         # @option arguments [Time] :timeout The maximum amount of time that the structure analysis can take.
         #  If the analysis is still running when the timeout expires, it will be stopped. Server default: 25s.
         # @option arguments [String] :timestamp_field The name of the field that contains the primary timestamp of each record in the text.
-        #  In particular, if the text was ingested into an index, this is the field that would be used to populate the +@timestamp+ field.If the format is +semi_structured_text+, this field must match the name of the appropriate extraction in the +grok_pattern+.
-        #  Therefore, for semi-structured text, it is best not to specify this parameter unless +grok_pattern+ is also specified.For structured text, if you specify this parameter, the field must exist within the text.If this parameter is not specified, the structure finder makes a decision about which field (if any) is the primary timestamp field.
+        #  In particular, if the text was ingested into an index, this is the field that would be used to populate the `@timestamp` field.If the format is `semi_structured_text`, this field must match the name of the appropriate extraction in the `grok_pattern`.
+        #  Therefore, for semi-structured text, it is best not to specify this parameter unless `grok_pattern` is also specified.For structured text, if you specify this parameter, the field must exist within the text.If this parameter is not specified, the structure finder makes a decision about which field (if any) is the primary timestamp field.
         #  For structured text, it is not compulsory to have a timestamp in the text.
         # @option arguments [String] :timestamp_format The Java time format of the timestamp field in the text.
         #  Only a subset of Java time format letter groups are supported:
-        #  - +a+
-        #  - +d+
-        #  - +dd+
-        #  - +EEE+
-        #  - +EEEE+
-        #  - +H+
-        #  - +HH+
-        #  - +h+
-        #  - +M+
-        #  - +MM+
-        #  - +MMM+
-        #  - +MMMM+
-        #  - +mm+
-        #  - +ss+
-        #  - +XX+
-        #  - +XXX+
-        #  - +yy+
-        #  - +yyyy+
-        #  - +zzz+
-        #  Additionally +S+ letter groups (fractional seconds) of length one to nine are supported providing they occur after +ss+ and are separated from the +ss+ by a period (+.+), comma (+,+), or colon (+:+).
-        #  Spacing and punctuation is also permitted with the exception a question mark (+?+), newline, and carriage return, together with literal text enclosed in single quotes.
-        #  For example, +MM/dd HH.mm.ss,SSSSSS 'in' yyyy+ is a valid override format.One valuable use case for this parameter is when the format is semi-structured text, there are multiple timestamp formats in the text, and you know which format corresponds to the primary timestamp, but you do not want to specify the full +grok_pattern+.
-        #  Another is when the timestamp format is one that the structure finder does not consider by default.If this parameter is not specified, the structure finder chooses the best format from a built-in set.If the special value +null+ is specified, the structure finder will not look for a primary timestamp in the text.
+        #  - `a`
+        #  - `d`
+        #  - `dd`
+        #  - `EEE`
+        #  - `EEEE`
+        #  - `H`
+        #  - `HH`
+        #  - `h`
+        #  - `M`
+        #  - `MM`
+        #  - `MMM`
+        #  - `MMMM`
+        #  - `mm`
+        #  - `ss`
+        #  - `XX`
+        #  - `XXX`
+        #  - `yy`
+        #  - `yyyy`
+        #  - `zzz`
+        #  Additionally `S` letter groups (fractional seconds) of length one to nine are supported providing they occur after `ss` and are separated from the `ss` by a period (`.`), comma (`,`), or colon (`:`).
+        #  Spacing and punctuation is also permitted with the exception a question mark (`?`), newline, and carriage return, together with literal text enclosed in single quotes.
+        #  For example, `MM/dd HH.mm.ss,SSSSSS 'in' yyyy` is a valid override format.One valuable use case for this parameter is when the format is semi-structured text, there are multiple timestamp formats in the text, and you know which format corresponds to the primary timestamp, but you do not want to specify the full `grok_pattern`.
+        #  Another is when the timestamp format is one that the structure finder does not consider by default.If this parameter is not specified, the structure finder chooses the best format from a built-in set.If the special value `null` is specified, the structure finder will not look for a primary timestamp in the text.
         #  When the format is semi-structured text, this will result in the structure finder treating the text as single-line messages.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
         # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/group/endpoint-text_structure

data/lib/elasticsearch/api/actions/text_structure/find_message_structure.rb

@@ -34,69 +34,80 @@ module Elasticsearch
         # Appropriate mappings for an Elasticsearch index, which you could use to ingest the text.
         # All this information can be calculated by the structure finder with no guidance.
         # However, you can optionally override some of the decisions about the text structure by specifying one or more query parameters.
-        # If the structure finder produces unexpected results, specify the +explain+ query parameter and an explanation will appear in the response.
+        # If the structure finder produces unexpected results, specify the `explain` query parameter and an explanation will appear in the response.
         # It helps determine why the returned structure was chosen.
         #
-        # @option arguments [String] :column_names If the format is +delimited+, you can specify the column names in a comma-separated list.
+        # @option arguments [String] :column_names If the format is `delimited`, you can specify the column names in a comma-separated list.
         #  If this parameter is not specified, the structure finder uses the column names from the header row of the text.
         #  If the text does not have a header role, columns are named "column1", "column2", "column3", for example.
-        # @option arguments [String] :delimiter If you the format is +delimited+, you can specify the character used to delimit the values in each row.
+        # @option arguments [String] :delimiter If you the format is `delimited`, you can specify the character used to delimit the values in each row.
         #  Only a single character is supported; the delimiter cannot have multiple characters.
-        #  By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (+|+).
+        #  By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (`|`).
         #  In this default scenario, all rows must have the same number of fields for the delimited format to be detected.
         #  If you specify a delimiter, up to 10% of the rows can have a different number of columns than the first row.
         # @option arguments [String] :ecs_compatibility The mode of compatibility with ECS compliant Grok patterns.
         #  Use this parameter to specify whether to use ECS Grok patterns instead of legacy ones when the structure finder creates a Grok pattern.
-        #  This setting primarily has an impact when a whole message Grok pattern such as +%{CATALINALOG}+ matches the input.
-        #  If the structure finder identifies a common structure but has no idea of meaning then generic field names such as +path+, +ipaddress+, +field1+, and +field2+ are used in the +grok_pattern+ output, with the intention that a user who knows the meanings rename these fields before using it. Server default: disabled.
-        # @option arguments [Boolean] :explain If this parameter is set to true, the response includes a field named +explanation+, which is an array of strings that indicate how the structure finder produced its result.
+        #  This setting primarily has an impact when a whole message Grok pattern such as `%{CATALINALOG}` matches the input.
+        #  If the structure finder identifies a common structure but has no idea of meaning then generic field names such as `path`, `ipaddress`, `field1`, and `field2` are used in the `grok_pattern` output, with the intention that a user who knows the meanings rename these fields before using it. Server default: disabled.
+        # @option arguments [Boolean] :explain If this parameter is set to true, the response includes a field named `explanation`, which is an array of strings that indicate how the structure finder produced its result.
         # @option arguments [String] :format The high level structure of the text.
         #  By default, the API chooses the format.
         #  In this default scenario, all rows must have the same number of fields for a delimited format to be detected.
-        #  If the format is +delimited+ and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row.
-        # @option arguments [String] :grok_pattern If the format is +semi_structured_text+, you can specify a Grok pattern that is used to extract fields from every message in the text.
-        #  The name of the timestamp field in the Grok pattern must match what is specified in the +timestamp_field+ parameter.
+        #  If the format is `delimited` and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row.
+        # @option arguments [String] :grok_pattern If the format is `semi_structured_text`, you can specify a Grok pattern that is used to extract fields from every message in the text.
+        #  The name of the timestamp field in the Grok pattern must match what is specified in the `timestamp_field` parameter.
         #  If that parameter is not specified, the name of the timestamp field in the Grok pattern must match "timestamp".
-        #  If +grok_pattern+ is not specified, the structure finder creates a Grok pattern.
-        # @option arguments [String] :quote If the format is +delimited+, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character.
+        #  If `grok_pattern` is not specified, the structure finder creates a Grok pattern.
+        # @option arguments [String] :quote If the format is `delimited`, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character.
         #  Only a single character is supported.
-        #  If this parameter is not specified, the default value is a double quote (+"+).
+        #  If this parameter is not specified, the default value is a double quote (`"`).
         #  If your delimited text format does not use quoting, a workaround is to set this argument to a character that does not appear anywhere in the sample.
-        # @option arguments [Boolean] :should_trim_fields If the format is +delimited+, you can specify whether values between delimiters should have whitespace trimmed from them.
-        #  If this parameter is not specified and the delimiter is pipe (+|+), the default value is true.
-        #  Otherwise, the default value is +false+.
+        # @option arguments [Boolean] :should_trim_fields If the format is `delimited`, you can specify whether values between delimiters should have whitespace trimmed from them.
+        #  If this parameter is not specified and the delimiter is pipe (`|`), the default value is true.
+        #  Otherwise, the default value is `false`.
         # @option arguments [Time] :timeout The maximum amount of time that the structure analysis can take.
         #  If the analysis is still running when the timeout expires, it will be stopped. Server default: 25s.
         # @option arguments [String] :timestamp_field The name of the field that contains the primary timestamp of each record in the text.
-        #  In particular, if the text was ingested into an index, this is the field that would be used to populate the +@timestamp+ field.If the format is +semi_structured_text+, this field must match the name of the appropriate extraction in the +grok_pattern+.
-        #  Therefore, for semi-structured text, it is best not to specify this parameter unless +grok_pattern+ is also specified.For structured text, if you specify this parameter, the field must exist within the text.If this parameter is not specified, the structure finder makes a decision about which field (if any) is the primary timestamp field.
+        #  In particular, if the text was ingested into an index, this is the field that would be used to populate the `@timestamp` field.If the format is `semi_structured_text`, this field must match the name of the appropriate extraction in the `grok_pattern`.
+        #  Therefore, for semi-structured text, it is best not to specify this parameter unless `grok_pattern` is also specified.For structured text, if you specify this parameter, the field must exist within the text.If this parameter is not specified, the structure finder makes a decision about which field (if any) is the primary timestamp field.
         #  For structured text, it is not compulsory to have a timestamp in the text.
         # @option arguments [String] :timestamp_format The Java time format of the timestamp field in the text.
         #  Only a subset of Java time format letter groups are supported:
-        #  - +a+
-        #  - +d+
-        #  - +dd+
-        #  - +EEE+
-        #  - +EEEE+
-        #  - +H+
-        #  - +HH+
-        #  - +h+
-        #  - +M+
-        #  - +MM+
-        #  - +MMM+
-        #  - +MMMM+
-        #  - +mm+
-        #  - +ss+
-        #  - +XX+
-        #  - +XXX+
-        #  - +yy+
-        #  - +yyyy+
-        #  - +zzz+
-        #  Additionally +S+ letter groups (fractional seconds) of length one to nine are supported providing they occur after +ss+ and are separated from the +ss+ by a period (+.+), comma (+,+), or colon (+:+).
-        #  Spacing and punctuation is also permitted with the exception a question mark (+?+), newline, and carriage return, together with literal text enclosed in single quotes.
-        #  For example, +MM/dd HH.mm.ss,SSSSSS 'in' yyyy+ is a valid override format.One valuable use case for this parameter is when the format is semi-structured text, there are multiple timestamp formats in the text, and you know which format corresponds to the primary timestamp, but you do not want to specify the full +grok_pattern+.
-        #  Another is when the timestamp format is one that the structure finder does not consider by default.If this parameter is not specified, the structure finder chooses the best format from a built-in set.If the special value +null+ is specified, the structure finder will not look for a primary timestamp in the text.
+        #  - `a`
+        #  - `d`
+        #  - `dd`
+        #  - `EEE`
+        #  - `EEEE`
+        #  - `H`
+        #  - `HH`
+        #  - `h`
+        #  - `M`
+        #  - `MM`
+        #  - `MMM`
+        #  - `MMMM`
+        #  - `mm`
+        #  - `ss`
+        #  - `XX`
+        #  - `XXX`
+        #  - `yy`
+        #  - `yyyy`
+        #  - `zzz`
+        #  Additionally `S` letter groups (fractional seconds) of length one to nine are supported providing they occur after `ss` and are separated from the `ss` by a period (`.`), comma (`,`), or colon (`:`).
+        #  Spacing and punctuation is also permitted with the exception a question mark (`?`), newline, and carriage return, together with literal text enclosed in single quotes.
+        #  For example, `MM/dd HH.mm.ss,SSSSSS 'in' yyyy` is a valid override format.One valuable use case for this parameter is when the format is semi-structured text, there are multiple timestamp formats in the text, and you know which format corresponds to the primary timestamp, but you do not want to specify the full `grok_pattern`.
+        #  Another is when the timestamp format is one that the structure finder does not consider by default.If this parameter is not specified, the structure finder chooses the best format from a built-in set.If the special value `null` is specified, the structure finder will not look for a primary timestamp in the text.
         #  When the format is semi-structured text, this will result in the structure finder treating the text as single-line messages.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         # @option arguments [Hash] :body request body
         #

data/lib/elasticsearch/api/actions/text_structure/find_structure.rb

@@ -38,33 +38,33 @@ module Elasticsearch
         #
         # @option arguments [String] :charset The text's character set.
         #  It must be a character set that is supported by the JVM that Elasticsearch uses.
-        #  For example, +UTF-8+, +UTF-16LE+, +windows-1252+, or +EUC-JP+.
+        #  For example, `UTF-8`, `UTF-16LE`, `windows-1252`, or `EUC-JP`.
         #  If this parameter is not specified, the structure finder chooses an appropriate character set.
-        # @option arguments [String] :column_names If you have set format to +delimited+, you can specify the column names in a comma-separated list.
+        # @option arguments [String] :column_names If you have set format to `delimited`, you can specify the column names in a comma-separated list.
         #  If this parameter is not specified, the structure finder uses the column names from the header row of the text.
         #  If the text does not have a header role, columns are named "column1", "column2", "column3", for example.
-        # @option arguments [String] :delimiter If you have set +format+ to +delimited+, you can specify the character used to delimit the values in each row.
+        # @option arguments [String] :delimiter If you have set `format` to `delimited`, you can specify the character used to delimit the values in each row.
         #  Only a single character is supported; the delimiter cannot have multiple characters.
-        #  By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (+|+).
+        #  By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (`|`).
         #  In this default scenario, all rows must have the same number of fields for the delimited format to be detected.
         #  If you specify a delimiter, up to 10% of the rows can have a different number of columns than the first row.
         # @option arguments [String] :ecs_compatibility The mode of compatibility with ECS compliant Grok patterns.
         #  Use this parameter to specify whether to use ECS Grok patterns instead of legacy ones when the structure finder creates a Grok pattern.
-        #  Valid values are +disabled+ and +v1+.
-        #  This setting primarily has an impact when a whole message Grok pattern such as +%{CATALINALOG}+ matches the input.
-        #  If the structure finder identifies a common structure but has no idea of meaning then generic field names such as +path+, +ipaddress+, +field1+, and +field2+ are used in the +grok_pattern+ output, with the intention that a user who knows the meanings rename these fields before using it. Server default: disabled.
-        # @option arguments [Boolean] :explain If this parameter is set to +true+, the response includes a field named explanation, which is an array of strings that indicate how the structure finder produced its result.
+        #  Valid values are `disabled` and `v1`.
+        #  This setting primarily has an impact when a whole message Grok pattern such as `%{CATALINALOG}` matches the input.
+        #  If the structure finder identifies a common structure but has no idea of meaning then generic field names such as `path`, `ipaddress`, `field1`, and `field2` are used in the `grok_pattern` output, with the intention that a user who knows the meanings rename these fields before using it. Server default: disabled.
+        # @option arguments [Boolean] :explain If this parameter is set to `true`, the response includes a field named explanation, which is an array of strings that indicate how the structure finder produced its result.
         #  If the structure finder produces unexpected results for some text, use this query parameter to help you determine why the returned structure was chosen.
         # @option arguments [String] :format The high level structure of the text.
-        #  Valid values are +ndjson+, +xml+, +delimited+, and +semi_structured_text+.
+        #  Valid values are `ndjson`, `xml`, `delimited`, and `semi_structured_text`.
         #  By default, the API chooses the format.
         #  In this default scenario, all rows must have the same number of fields for a delimited format to be detected.
-        #  If the format is set to +delimited+ and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row.
-        # @option arguments [String] :grok_pattern If you have set +format+ to +semi_structured_text+, you can specify a Grok pattern that is used to extract fields from every message in the text.
-        #  The name of the timestamp field in the Grok pattern must match what is specified in the +timestamp_field+ parameter.
+        #  If the format is set to `delimited` and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row.
+        # @option arguments [String] :grok_pattern If you have set `format` to `semi_structured_text`, you can specify a Grok pattern that is used to extract fields from every message in the text.
+        #  The name of the timestamp field in the Grok pattern must match what is specified in the `timestamp_field` parameter.
         #  If that parameter is not specified, the name of the timestamp field in the Grok pattern must match "timestamp".
-        #  If +grok_pattern+ is not specified, the structure finder creates a Grok pattern.
-        # @option arguments [Boolean] :has_header_row If you have set +format+ to +delimited+, you can use this parameter to indicate whether the column names are in the first row of the text.
+        #  If `grok_pattern` is not specified, the structure finder creates a Grok pattern.
+        # @option arguments [Boolean] :has_header_row If you have set `format` to `delimited`, you can use this parameter to indicate whether the column names are in the first row of the text.
         #  If this parameter is not specified, the structure finder guesses based on the similarity of the first row of the text to other rows.
         # @option arguments [Integer] :line_merge_size_limit The maximum number of characters in a message when lines are merged to form messages while analyzing semi-structured text.
         #  If you have extremely long messages you may need to increase this, but be aware that this may lead to very long processing times if the way to group lines into messages is misdetected. Server default: 10000.
@@ -73,43 +73,43 @@ module Elasticsearch
         #  If the value of this parameter is greater than the number of lines in the text, the analysis proceeds (as long as there are at least two lines in the text) for all of the lines.NOTE: The number of lines and the variation of the lines affects the speed of the analysis.
         #  For example, if you upload text where the first 1000 lines are all variations on the same message, the analysis will find more commonality than would be seen with a bigger sample.
         #  If possible, however, it is more efficient to upload sample text with more variety in the first 1000 lines than to request analysis of 100000 lines to achieve some variety. Server default: 1000.
-        # @option arguments [String] :quote If you have set +format+ to +delimited+, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character.
+        # @option arguments [String] :quote If you have set `format` to `delimited`, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character.
         #  Only a single character is supported.
-        #  If this parameter is not specified, the default value is a double quote (+"+).
+        #  If this parameter is not specified, the default value is a double quote (`"`).
         #  If your delimited text format does not use quoting, a workaround is to set this argument to a character that does not appear anywhere in the sample.
-        # @option arguments [Boolean] :should_trim_fields If you have set +format+ to +delimited+, you can specify whether values between delimiters should have whitespace trimmed from them.
-        #  If this parameter is not specified and the delimiter is pipe (+|+), the default value is +true+.
-        #  Otherwise, the default value is +false+.
+        # @option arguments [Boolean] :should_trim_fields If you have set `format` to `delimited`, you can specify whether values between delimiters should have whitespace trimmed from them.
+        #  If this parameter is not specified and the delimiter is pipe (`|`), the default value is `true`.
+        #  Otherwise, the default value is `false`.
         # @option arguments [Time] :timeout The maximum amount of time that the structure analysis can take.
         #  If the analysis is still running when the timeout expires then it will be stopped. Server default: 25s.
         # @option arguments [String] :timestamp_field The name of the field that contains the primary timestamp of each record in the text.
-        #  In particular, if the text were ingested into an index, this is the field that would be used to populate the +@timestamp+ field.If the +format+ is +semi_structured_text+, this field must match the name of the appropriate extraction in the +grok_pattern+.
-        #  Therefore, for semi-structured text, it is best not to specify this parameter unless +grok_pattern+ is also specified.For structured text, if you specify this parameter, the field must exist within the text.If this parameter is not specified, the structure finder makes a decision about which field (if any) is the primary timestamp field.
+        #  In particular, if the text were ingested into an index, this is the field that would be used to populate the `@timestamp` field.If the `format` is `semi_structured_text`, this field must match the name of the appropriate extraction in the `grok_pattern`.
+        #  Therefore, for semi-structured text, it is best not to specify this parameter unless `grok_pattern` is also specified.For structured text, if you specify this parameter, the field must exist within the text.If this parameter is not specified, the structure finder makes a decision about which field (if any) is the primary timestamp field.
         #  For structured text, it is not compulsory to have a timestamp in the text.
         # @option arguments [String] :timestamp_format The Java time format of the timestamp field in the text.Only a subset of Java time format letter groups are supported:
-        #  - +a+
-        #  - +d+
-        #  - +dd+
-        #  - +EEE+
-        #  - +EEEE+
-        #  - +H+
-        #  - +HH+
-        #  - +h+
-        #  - +M+
-        #  - +MM+
-        #  - +MMM+
-        #  - +MMMM+
-        #  - +mm+
-        #  - +ss+
-        #  - +XX+
-        #  - +XXX+
-        #  - +yy+
-        #  - +yyyy+
-        #  - +zzz+
-        #  Additionally +S+ letter groups (fractional seconds) of length one to nine are supported providing they occur after +ss+ and separated from the +ss+ by a +.+, +,+ or +:+.
-        #  Spacing and punctuation is also permitted with the exception of +?+, newline and carriage return, together with literal text enclosed in single quotes.
-        #  For example, +MM/dd HH.mm.ss,SSSSSS 'in' yyyy+ is a valid override format.One valuable use case for this parameter is when the format is semi-structured text, there are multiple timestamp formats in the text, and you know which format corresponds to the primary timestamp, but you do not want to specify the full +grok_pattern+.
-        #  Another is when the timestamp format is one that the structure finder does not consider by default.If this parameter is not specified, the structure finder chooses the best format from a built-in set.If the special value +null+ is specified the structure finder will not look for a primary timestamp in the text.
+        #  - `a`
+        #  - `d`
+        #  - `dd`
+        #  - `EEE`
+        #  - `EEEE`
+        #  - `H`
+        #  - `HH`
+        #  - `h`
+        #  - `M`
+        #  - `MM`
+        #  - `MMM`
+        #  - `MMMM`
+        #  - `mm`
+        #  - `ss`
+        #  - `XX`
+        #  - `XXX`
+        #  - `yy`
+        #  - `yyyy`
+        #  - `zzz`
+        #  Additionally `S` letter groups (fractional seconds) of length one to nine are supported providing they occur after `ss` and separated from the `ss` by a `.`, `,` or `:`.
+        #  Spacing and punctuation is also permitted with the exception of `?`, newline and carriage return, together with literal text enclosed in single quotes.
+        #  For example, `MM/dd HH.mm.ss,SSSSSS 'in' yyyy` is a valid override format.One valuable use case for this parameter is when the format is semi-structured text, there are multiple timestamp formats in the text, and you know which format corresponds to the primary timestamp, but you do not want to specify the full `grok_pattern`.
+        #  Another is when the timestamp format is one that the structure finder does not consider by default.If this parameter is not specified, the structure finder chooses the best format from a built-in set.If the special value `null` is specified the structure finder will not look for a primary timestamp in the text.
         #  When the format is semi-structured text this will result in the structure finder treating the text as single-line messages.
         # @option arguments [Hash] :headers Custom HTTP headers
         # @option arguments [Hash] :body text_files

data/lib/elasticsearch/api/actions/text_structure/test_grok_pattern.rb

@@ -28,7 +28,18 @@ module Elasticsearch
         #
         # @option arguments [String] :ecs_compatibility The mode of compatibility with ECS compliant Grok patterns.
         #  Use this parameter to specify whether to use ECS Grok patterns instead of legacy ones when the structure finder creates a Grok pattern.
-        #  Valid values are +disabled+ and +v1+. Server default: disabled.
+        #  Valid values are `disabled` and `v1`. Server default: disabled.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         # @option arguments [Hash] :body request body
         #

data/lib/elasticsearch/api/actions/transform/delete_transform.rb

@@ -30,6 +30,17 @@ module Elasticsearch
         # @option arguments [Boolean] :delete_dest_index If this value is true, the destination index is deleted together with the transform. If false, the destination
         #  index will not be deleted
         # @option arguments [Time] :timeout Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Server default: 30s.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
         # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-delete-transform

data/lib/elasticsearch/api/actions/transform/get_node_stats.rb

@@ -34,14 +34,9 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body = arguments.delete(:body)
-
-          method = if body
-                     Elasticsearch::API::HTTP_POST
-                   else
-                     Elasticsearch::API::HTTP_GET
-                   end
+          body = nil
 
+          method = Elasticsearch::API::HTTP_GET
           path   = '_transform/_node_stats'
           params = {}
 

data/lib/elasticsearch/api/actions/transform/get_transform.rb

@@ -27,8 +27,8 @@ module Elasticsearch
         #
         # @option arguments [String, Array<String>] :transform_id Identifier for the transform. It can be a transform identifier or a
         #  wildcard expression. You can get information for all transforms by using
-        #  +_all+, by specifying +*+ as the +<transform_id>+, or by omitting the
-        #  +<transform_id>+.
+        #  `_all`, by specifying `*` as the `<transform_id>`, or by omitting the
+        #  `<transform_id>`.
         # @option arguments [Boolean] :allow_no_match Specifies what to do when the request:
         #  - Contains wildcard expressions and there are no transforms that match.
         #  - Contains the _all string or no identifiers and there are no matches.
@@ -40,6 +40,17 @@ module Elasticsearch
         # @option arguments [Boolean] :exclude_generated Excludes fields that were automatically added when creating the
         #  transform. This allows the configuration to be in an acceptable format to
         #  be retrieved and then added to another cluster.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
         # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-get-transform

data/lib/elasticsearch/api/actions/transform/get_transform_stats.rb

@@ -27,8 +27,8 @@ module Elasticsearch
         #
         # @option arguments [String, Array<String>] :transform_id Identifier for the transform. It can be a transform identifier or a
         #  wildcard expression. You can get information for all transforms by using
-        #  +_all+, by specifying +*+ as the +<transform_id>+, or by omitting the
-        #  +<transform_id>+. (*Required*)
+        #  `_all`, by specifying `*` as the `<transform_id>`, or by omitting the
+        #  `<transform_id>`. (*Required*)
         # @option arguments [Boolean] :allow_no_match Specifies what to do when the request:
         #  - Contains wildcard expressions and there are no transforms that match.
         #  - Contains the _all string or no identifiers and there are no matches.
@@ -38,6 +38,17 @@ module Elasticsearch
         # @option arguments [Integer] :from Skips the specified number of transforms. Server default: 0.
         # @option arguments [Integer] :size Specifies the maximum number of transforms to obtain. Server default: 100.
         # @option arguments [Time] :timeout Controls the time to wait for the stats
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
         # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-get-transform-stats

data/lib/elasticsearch/api/actions/transform/preview_transform.rb

@@ -32,6 +32,17 @@ module Elasticsearch
         #  configuration details in the request body.
         # @option arguments [Time] :timeout Period to wait for a response. If no response is received before the
         #  timeout expires, the request fails and returns an error. Server default: 30s.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         # @option arguments [Hash] :body request body
         #

data/lib/elasticsearch/api/actions/transform/put_transform.rb

@@ -28,18 +28,18 @@ module Elasticsearch
         # a data frame). The ID for each document in the data frame is generated from a hash of the entity, so there is a
         # unique row per entity.
         # You must choose either the latest or pivot method for your transform; you cannot use both in a single transform. If
-        # you choose to use the pivot method for your transform, the entities are defined by the set of +group_by+ fields in
-        # the pivot object. If you choose to use the latest method, the entities are defined by the +unique_key+ field values
+        # you choose to use the pivot method for your transform, the entities are defined by the set of `group_by` fields in
+        # the pivot object. If you choose to use the latest method, the entities are defined by the `unique_key` field values
         # in the latest object.
-        # You must have +create_index+, +index+, and +read+ privileges on the destination index and +read+ and
-        # +view_index_metadata+ privileges on the source indices. When Elasticsearch security features are enabled, the
+        # You must have `create_index`, `index`, and `read` privileges on the destination index and `read` and
+        # `view_index_metadata` privileges on the source indices. When Elasticsearch security features are enabled, the
         # transform remembers which roles the user that created it had at the time of creation and uses those same roles. If
         # those roles do not have the required privileges on the source and destination indices, the transform fails when it
         # attempts unauthorized operations.
         # NOTE: You must use Kibana or this API to create a transform. Do not add a transform directly into any
-        # +.transform-internal*+ indices using the Elasticsearch index API. If Elasticsearch security features are enabled, do
-        # not give users any privileges on +.transform-internal*+ indices. If you used transforms prior to 7.5, also do not
-        # give users any privileges on +.data-frame-internal*+ indices.
+        # `.transform-internal*` indices using the Elasticsearch index API. If Elasticsearch security features are enabled, do
+        # not give users any privileges on `.transform-internal*` indices. If you used transforms prior to 7.5, also do not
+        # give users any privileges on `.data-frame-internal*` indices.
         #
         # @option arguments [String] :transform_id Identifier for the transform. This identifier can contain lowercase alphanumeric characters (a-z and 0-9),
         #  hyphens, and underscores. It has a 64 character limit and must start and end with alphanumeric characters. (*Required*)
@@ -49,6 +49,17 @@ module Elasticsearch
         #  until after the transform is created. The validations are always run when you start the transform, however, with
         #  the exception of privilege checks.
         # @option arguments [Time] :timeout Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Server default: 30s.
+        # @option arguments [Boolean] :error_trace When set to `true` Elasticsearch will include the full stack trace of errors
+        #  when they occur.
+        # @option arguments [String, Array<String>] :filter_path Comma-separated list of filters in dot notation which reduce the response
+        #  returned by Elasticsearch.
+        # @option arguments [Boolean] :human When set to `true` will return statistics in a format suitable for humans.
+        #  For example `"exists_time": "1h"` for humans and
+        #  `"eixsts_time_in_millis": 3600000` for computers. When disabled the human
+        #  readable values will be omitted. This makes sense for responses being consumed
+        #  only by machines.
+        # @option arguments [Boolean] :pretty If set to `true` the returned JSON will be "pretty-formatted". Only use
+        #  this option for debugging only.
         # @option arguments [Hash] :headers Custom HTTP headers
         # @option arguments [Hash] :body request body
         #