@elastic/schemas 0.4.4 → 0.5.0

package/src/es/json/esql._types.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"esql._types__EsqlFormat":{"enum":["csv","json","tsv","txt","yaml","cbor","smile","arrow"]},"esql._types__ESQLParams":{"oneOf":[{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__SingleOrMultiValue"}},{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__NamedValue"}}]},"esql._types__SingleOrMultiValue":{"oneOf":[{"$ref":"./_types.json#/$defs/_types__FieldValue"},{"type":"array","items":{"$ref":"./_types.json#/$defs/_types__FieldValue"}}]},"esql._types__NamedValue":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__NamedParameterValue"}},"esql._types__NamedParameterValue":{"oneOf":[{"$ref":"./esql._types.json#/$defs/esql._types__SingleOrMultiValue"},{"$ref":"./esql._types.json#/$defs/esql._types__ClassifiedNamedParameter"}],"description":"The value of a named ES|QL query parameter.\nIt is either a literal single or multi value, or a single-key object that classifies how\nthe parameter is interpreted."},"esql._types__ClassifiedNamedParameter":{"type":"object","properties":{"value":{"$ref":"./esql._types.json#/$defs/esql._types__SingleOrMultiValue","description":"Interpret the parameter as a literal value."},"identifier":{"type":"string","description":"Interpret the parameter as an identifier, such as a field or function name."},"pattern":{"type":"string","description":"Interpret the parameter as a pattern, such as an index or field name pattern."}},"description":"A named ES|QL query parameter supplied in its classified form.\nExactly one of `value`, `identifier`, or `pattern` must be set."},"esql._types__TableValuesContainer":{"type":"object","properties":{"integer":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesIntegerValue"}},"keyword":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesKeywordValue"}},"long":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesLongValue"}},"double":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesLongDouble"}}}},"esql._types__TableValuesIntegerValue":{"oneOf":[{"type":"number"},{"type":"array","items":{"type":"number"}}]},"esql._types__TableValuesKeywordValue":{"oneOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}]},"esql._types__TableValuesLongValue":{"oneOf":[{"type":"number"},{"type":"array","items":{"type":"number"}}]},"esql._types__TableValuesLongDouble":{"oneOf":[{"type":"number"},{"type":"array","items":{"type":"number"}}]},"esql._types__EsqlQuerySettings":{"type":"object","properties":{"time_zone":{"type":"string","description":"The default timezone to be used in the query.\nIt defaults to UTC and overrides the `time_zone` request parameter."},"approximation":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlApproximation","description":"Enables query approximation if possible for the query.\n`false` (the default) disables query approximation and `true` enables it with default settings.\nA map value enables query approximation with custom settings."},"column_metadata":{"$ref":"./_spec_utils.json#/$defs/_spec_utils__Stringified","description":"When enabled, column metadata is added to the query response as additional `_meta` properties.\nCurrently, only `_meta.bucket` is added for columns corresponding to the `BUCKET` function, containing the bucket interval and unit for queries where it can be determined."}},"description":"Per-query settings supplied through the request body.\nThis is the request-body equivalent of the in-query `SET` command.\nOnly settings that are exposed as request-body parameters can be set here; other `SET`-only\nsettings (such as `unmapped_fields`) must be supplied in the query itself."},"esql._types__EsqlApproximation":{"oneOf":[{"type":"boolean"},{"$ref":"./esql._types.json#/$defs/esql._types__EsqlApproximationSettings"}],"description":"The `approximation` query setting.\nIt can be a boolean that toggles query approximation with default settings, or a map that enables it with custom settings."},"esql._types__EsqlApproximationSettings":{"type":"object","properties":{"rows":{"type":"number","description":"The number of sampled rows used for approximating the query.\nIt must be at least 10,000. A null value uses the system default."},"confidence_level":{"type":"number","description":"The confidence level of the computed confidence intervals.\nA null value disables computing confidence intervals."}}},"esql._types__AsyncEsqlResult":{"type":"object","properties":{"took":{},"is_partial":{"type":"boolean"},"all_columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"values":{"type":"array","items":{"type":"array","items":{"$ref":"./_types.json#/$defs/_types__FieldValue"}}},"_clusters":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterInfo","description":"Cross-cluster search information. Present if `include_ccs_metadata` was `true` in the request\nand a cross-cluster search was performed."},"profile":{"description":"Profiling information. Present if `profile` was `true` in the request.\nThe contents of this field are currently unstable."},"id":{"type":"string","description":"The ID of the async query, to be used in subsequent requests to check the status or retrieve results.\n\nAlso available in the `X-Elasticsearch-Async-Id` HTTP header."},"is_running":{"type":"boolean","description":"Indicates whether the async query is still running or has completed.\n\nAlso available in the `X-Elasticsearch-Async-Is-Running` HTTP header."}},"required":["columns","values","is_running"]},"esql._types__EsqlColumnInfo":{"type":"object","properties":{"name":{"type":"string"},"type":{"type":"string"}},"required":["name","type"]},"esql._types__EsqlClusterInfo":{"type":"object","properties":{"total":{"type":"number"},"successful":{"type":"number"},"running":{"type":"number"},"skipped":{"type":"number"},"partial":{"type":"number"},"failed":{"type":"number"},"details":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterDetails"}}},"required":["total","successful","running","skipped","partial","failed","details"]},"esql._types__EsqlClusterDetails":{"type":"object","properties":{"status":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterStatus"},"indices":{"type":"string"},"took":{},"_shards":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlShardInfo"},"failures":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlShardFailure"}}},"required":["status","indices"]},"esql._types__EsqlClusterStatus":{"enum":["running","successful","partial","skipped","failed"]},"esql._types__EsqlShardInfo":{"type":"object","properties":{"total":{"type":"number"},"successful":{"type":"number"},"skipped":{"type":"number"},"failed":{"type":"number"}},"required":["total"]},"esql._types__EsqlShardFailure":{"type":"object","properties":{"shard":{"type":"number"},"index":{"oneOf":[{"type":"string"},{"type":"null"}]},"node":{"type":"string"},"reason":{"$ref":"./_types.json#/$defs/_types__ErrorCause"}},"required":["shard","index","reason"]},"esql._types__EsqlResult":{"type":"object","properties":{"took":{},"is_partial":{"type":"boolean"},"all_columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"values":{"type":"array","items":{"type":"array","items":{"$ref":"./_types.json#/$defs/_types__FieldValue"}}},"_clusters":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterInfo","description":"Cross-cluster search information. Present if `include_ccs_metadata` was `true` in the request\nand a cross-cluster search was performed."},"profile":{"description":"Profiling information. Present if `profile` was `true` in the request.\nThe contents of this field are currently unstable."}},"required":["columns","values"]},"esql._types__ESQLView":{"type":"object","properties":{"name":{"type":"string","description":"The name of the ES|QL view"},"query":{"type":"string","description":"The ES|QL query"}},"required":["name","query"],"description":"A non-materialized ES|QL view."}}}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"esql._types__EsqlFormat":{"enum":["csv","json","tsv","txt","yaml","cbor","smile","arrow"]},"esql._types__ESQLParams":{"anyOf":[{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__SingleOrMultiValue"}},{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__NamedValue"}}]},"esql._types__SingleOrMultiValue":{"anyOf":[{"$ref":"./_types.json#/$defs/_types__FieldValue"},{"type":"array","items":{"$ref":"./_types.json#/$defs/_types__FieldValue"}}]},"esql._types__NamedValue":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__NamedParameterValue"}},"esql._types__NamedParameterValue":{"anyOf":[{"$ref":"./esql._types.json#/$defs/esql._types__SingleOrMultiValue"},{"$ref":"./esql._types.json#/$defs/esql._types__ClassifiedNamedParameter"}],"description":"The value of a named ES|QL query parameter.\nIt is either a literal single or multi value, or a single-key object that classifies how\nthe parameter is interpreted."},"esql._types__ClassifiedNamedParameter":{"type":"object","properties":{"value":{"$ref":"./esql._types.json#/$defs/esql._types__SingleOrMultiValue","description":"Interpret the parameter as a literal value."},"identifier":{"type":"string","description":"Interpret the parameter as an identifier, such as a field or function name."},"pattern":{"type":"string","description":"Interpret the parameter as a pattern, such as an index or field name pattern."}},"description":"A named ES|QL query parameter supplied in its classified form.\nExactly one of `value`, `identifier`, or `pattern` must be set."},"esql._types__TableValuesContainer":{"type":"object","properties":{"integer":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesIntegerValue"}},"keyword":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesKeywordValue"}},"long":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesLongValue"}},"double":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesLongDouble"}}}},"esql._types__TableValuesIntegerValue":{"anyOf":[{"type":"number"},{"type":"array","items":{"type":"number"}}]},"esql._types__TableValuesKeywordValue":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}]},"esql._types__TableValuesLongValue":{"anyOf":[{"type":"number"},{"type":"array","items":{"type":"number"}}]},"esql._types__TableValuesLongDouble":{"anyOf":[{"type":"number"},{"type":"array","items":{"type":"number"}}]},"esql._types__EsqlQuerySettings":{"type":"object","properties":{"time_zone":{"type":"string","description":"The default timezone to be used in the query.\nIt defaults to UTC and overrides the `time_zone` request parameter."},"approximation":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlApproximation","description":"Enables query approximation if possible for the query.\n`false` (the default) disables query approximation and `true` enables it with default settings.\nA map value enables query approximation with custom settings."},"column_metadata":{"$ref":"./_spec_utils.json#/$defs/_spec_utils__Stringified","description":"When enabled, column metadata is added to the query response as additional `_meta` properties.\nCurrently, only `_meta.bucket` is added for columns corresponding to the `BUCKET` function, containing the bucket interval and unit for queries where it can be determined."}},"description":"Per-query settings supplied through the request body.\nThis is the request-body equivalent of the in-query `SET` command.\nOnly settings that are exposed as request-body parameters can be set here; other `SET`-only\nsettings (such as `unmapped_fields`) must be supplied in the query itself."},"esql._types__EsqlApproximation":{"anyOf":[{"type":"boolean"},{"$ref":"./esql._types.json#/$defs/esql._types__EsqlApproximationSettings"}],"description":"The `approximation` query setting.\nIt can be a boolean that toggles query approximation with default settings, or a map that enables it with custom settings."},"esql._types__EsqlApproximationSettings":{"type":"object","properties":{"rows":{"type":"number","description":"The number of sampled rows used for approximating the query.\nIt must be at least 10,000. A null value uses the system default."},"confidence_level":{"type":"number","description":"The confidence level of the computed confidence intervals.\nA null value disables computing confidence intervals."}}},"esql._types__AsyncEsqlResult":{"type":"object","properties":{"took":{},"is_partial":{"type":"boolean"},"all_columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"values":{"type":"array","items":{"type":"array","items":{"$ref":"./_types.json#/$defs/_types__FieldValue"}}},"_clusters":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterInfo","description":"Cross-cluster search information. Present if `include_ccs_metadata` was `true` in the request\nand a cross-cluster search was performed."},"profile":{"description":"Profiling information. Present if `profile` was `true` in the request.\nThe contents of this field are currently unstable."},"id":{"type":"string","description":"The ID of the async query, to be used in subsequent requests to check the status or retrieve results.\n\nAlso available in the `X-Elasticsearch-Async-Id` HTTP header."},"is_running":{"type":"boolean","description":"Indicates whether the async query is still running or has completed.\n\nAlso available in the `X-Elasticsearch-Async-Is-Running` HTTP header."}},"required":["columns","values","is_running"]},"esql._types__EsqlColumnInfo":{"type":"object","properties":{"name":{"type":"string"},"type":{"type":"string"}},"required":["name","type"]},"esql._types__EsqlClusterInfo":{"type":"object","properties":{"total":{"type":"number"},"successful":{"type":"number"},"running":{"type":"number"},"skipped":{"type":"number"},"partial":{"type":"number"},"failed":{"type":"number"},"details":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterDetails"}}},"required":["total","successful","running","skipped","partial","failed","details"]},"esql._types__EsqlClusterDetails":{"type":"object","properties":{"status":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterStatus"},"indices":{"type":"string"},"took":{},"_shards":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlShardInfo"},"failures":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlShardFailure"}}},"required":["status","indices"]},"esql._types__EsqlClusterStatus":{"enum":["running","successful","partial","skipped","failed"]},"esql._types__EsqlShardInfo":{"type":"object","properties":{"total":{"type":"number"},"successful":{"type":"number"},"skipped":{"type":"number"},"failed":{"type":"number"}},"required":["total"]},"esql._types__EsqlShardFailure":{"type":"object","properties":{"shard":{"type":"number"},"index":{"anyOf":[{"type":"string"},{"type":"null"}]},"node":{"type":"string"},"reason":{"$ref":"./_types.json#/$defs/_types__ErrorCause"}},"required":["shard","index","reason"]},"esql._types__EsqlResult":{"type":"object","properties":{"took":{},"is_partial":{"type":"boolean"},"all_columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"columns":{"type":"array","items":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlColumnInfo"}},"values":{"type":"array","items":{"type":"array","items":{"$ref":"./_types.json#/$defs/_types__FieldValue"}}},"_clusters":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlClusterInfo","description":"Cross-cluster search information. Present if `include_ccs_metadata` was `true` in the request\nand a cross-cluster search was performed."},"profile":{"description":"Profiling information. Present if `profile` was `true` in the request.\nThe contents of this field are currently unstable."}},"required":["columns","values"]},"esql._types__ESQLView":{"type":"object","properties":{"name":{"type":"string","description":"The name of the ES|QL view"},"query":{"type":"string","description":"The ES|QL query"}},"required":["name","query"],"description":"A non-materialized ES|QL view."}}}

package/src/es/json/esql.async_query.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"esql.async_query","type":"object","properties":{"columnar":{"type":"boolean","description":"By default, ES|QL returns results as rows. For example, FROM returns each individual document as one row. For the JSON, YAML, CBOR and smile formats, ES|QL can return the results in a columnar fashion where one row represents all the values of a certain column in the results.","x-found-in":"body"},"filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Specify a Query DSL query in the filter parameter to filter the set of documents that an ES|QL query runs on.","x-found-in":"body"},"time_zone":{"type":"string","description":"Sets the default timezone of the query.","x-found-in":"body"},"locale":{"type":"string","description":"Returns results (especially dates) formatted per the conventions of the locale.","x-found-in":"body"},"params":{"$ref":"./esql._types.json#/$defs/esql._types__ESQLParams","description":"To avoid any attempts of hacking or code injection, extract the values in a separate list of parameters. Use question mark placeholders (?) in the query string for each of the parameters.","x-found-in":"body"},"profile":{"type":"boolean","description":"If provided and `true` the response will include an extra `profile` object\nwith information on how the query was executed. This information is for human debugging\nand its format can change at any time but it can give some insight into the performance\nof each part of the query.","x-found-in":"body"},"query":{"type":"string","description":"The ES|QL query API accepts an ES|QL query string in the query parameter, runs it, and returns the results.","x-found-in":"body"},"tables":{"type":"object","additionalProperties":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesContainer"}},"description":"Tables to use with the LOOKUP operation. The top level key is the table\nname and the next level key is the column name.","x-found-in":"body"},"include_ccs_metadata":{"type":"boolean","description":"When set to `true` and performing a cross-cluster/cross-project query, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.","x-found-in":"body"},"include_execution_metadata":{"type":"boolean","description":"When set to `true`, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.\nThis is similar to `include_ccs_metadata`, but it also returns metadata when the query is not CCS/CPS","x-found-in":"body"},"wait_for_completion_timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period to wait for the request to finish.\nBy default, the request waits for 1 second for the query results.\nIf the query completes during this period, results are returned\nOtherwise, a query ID is returned that can later be used to retrieve the results.","x-found-in":"body"},"keep_alive":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period for which the query and its results are stored in the cluster.\nThe default period is five days.\nWhen this period expires, the query and its results are deleted, even if the query is still ongoing.\nIf the `keep_on_completion` parameter is false, Elasticsearch only stores async queries that do not complete within the period set by the `wait_for_completion_timeout` parameter, regardless of this value.","x-found-in":"body"},"keep_on_completion":{"type":"boolean","description":"Indicates whether the query and its results are stored in the cluster.\nIf false, the query and its results are stored in the cluster only if the request does not complete during the period set by the `wait_for_completion_timeout` parameter.","x-found-in":"body"},"settings":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlQuerySettings","description":"Per-query settings, the request-body equivalent of the in-query `SET` command.\nFor example, `time_zone` can be supplied here instead of as a top-level field.","x-found-in":"body"},"allow_partial_results":{"type":"boolean","description":"If `true`, partial results will be returned if there are shard failures, but the query can continue to execute on other clusters and shards.\nIf `false`, the query will fail if there are any failures.\n\nTo override the default behavior, you can set the `esql.query.allow_partial_results` cluster setting to `false`.","x-found-in":"query"},"delimiter":{"type":"string","description":"The character to use between values within a CSV row.\nIt is valid only for the CSV format.","x-found-in":"query"},"drop_null_columns":{"type":"boolean","description":"Indicates whether columns that are entirely `null` will be removed from the `columns` and `values` portion of the results.\nIf `true`, the response will include an extra section under the name `all_columns` which has the name of all the columns.","x-found-in":"query"},"format":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlFormat","description":"A short version of the Accept header, e.g. json, yaml.\n\n`csv`, `tsv`, and `txt` formats will return results in a tabular format, excluding other metadata fields from the response.\n\nFor async requests, nothing will be returned if the async query doesn't finish within the timeout.\nThe query ID and running status are available in the `X-Elasticsearch-Async-Id` and `X-Elasticsearch-Async-Is-Running` HTTP headers of the response, respectively.","x-found-in":"query"}},"required":["query"],"description":"Run an async ES|QL query.\n\nAsynchronously run an ES|QL (Elasticsearch query language) query, monitor its progress, and retrieve results when they become available.\n\nThe API accepts the same parameters and request body as the synchronous query API, along with additional async related properties."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"esql.async_query","type":"object","properties":{"allow_partial_results":{"type":"boolean","description":"If `true`, partial results will be returned if there are shard failures, but the query can continue to execute on other clusters and shards.\nIf `false`, the query will fail if there are any failures.\n\nTo override the default behavior, you can set the `esql.query.allow_partial_results` cluster setting to `false`.","x-found-in":"query"},"delimiter":{"type":"string","description":"The character to use between values within a CSV row.\nIt is valid only for the CSV format.","x-found-in":"query"},"drop_null_columns":{"type":"boolean","description":"Indicates whether columns that are entirely `null` will be removed from the `columns` and `values` portion of the results.\nIf `true`, the response will include an extra section under the name `all_columns` which has the name of all the columns.","x-found-in":"query"},"format":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlFormat","description":"A short version of the Accept header, e.g. json, yaml.\n\n`csv`, `tsv`, and `txt` formats will return results in a tabular format, excluding other metadata fields from the response.\n\nFor async requests, nothing will be returned if the async query doesn't finish within the timeout.\nThe query ID and running status are available in the `X-Elasticsearch-Async-Id` and `X-Elasticsearch-Async-Is-Running` HTTP headers of the response, respectively.","x-found-in":"query"},"columnar":{"type":"boolean","description":"By default, ES|QL returns results as rows. For example, FROM returns each individual document as one row. For the JSON, YAML, CBOR and smile formats, ES|QL can return the results in a columnar fashion where one row represents all the values of a certain column in the results.","x-found-in":"body"},"filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Specify a Query DSL query in the filter parameter to filter the set of documents that an ES|QL query runs on.","x-found-in":"body"},"time_zone":{"type":"string","description":"Sets the default timezone of the query.","x-found-in":"body"},"locale":{"type":"string","description":"Returns results (especially dates) formatted per the conventions of the locale.","x-found-in":"body"},"params":{"$ref":"./esql._types.json#/$defs/esql._types__ESQLParams","description":"To avoid any attempts of hacking or code injection, extract the values in a separate list of parameters. Use question mark placeholders (?) in the query string for each of the parameters.","x-found-in":"body"},"profile":{"type":"boolean","description":"If provided and `true` the response will include an extra `profile` object\nwith information on how the query was executed. This information is for human debugging\nand its format can change at any time but it can give some insight into the performance\nof each part of the query.","x-found-in":"body"},"query":{"type":"string","description":"The ES|QL query API accepts an ES|QL query string in the query parameter, runs it, and returns the results.","x-found-in":"body"},"tables":{"type":"object","additionalProperties":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesContainer"}},"description":"Tables to use with the LOOKUP operation. The top level key is the table\nname and the next level key is the column name.","x-found-in":"body"},"include_ccs_metadata":{"type":"boolean","description":"When set to `true` and performing a cross-cluster/cross-project query, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.","x-found-in":"body"},"include_execution_metadata":{"type":"boolean","description":"When set to `true`, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.\nThis is similar to `include_ccs_metadata`, but it also returns metadata when the query is not CCS/CPS","x-found-in":"body"},"wait_for_completion_timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period to wait for the request to finish.\nBy default, the request waits for 1 second for the query results.\nIf the query completes during this period, results are returned\nOtherwise, a query ID is returned that can later be used to retrieve the results.","x-found-in":"body"},"keep_alive":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period for which the query and its results are stored in the cluster.\nThe default period is five days.\nWhen this period expires, the query and its results are deleted, even if the query is still ongoing.\nIf the `keep_on_completion` parameter is false, Elasticsearch only stores async queries that do not complete within the period set by the `wait_for_completion_timeout` parameter, regardless of this value.","x-found-in":"body"},"keep_on_completion":{"type":"boolean","description":"Indicates whether the query and its results are stored in the cluster.\nIf false, the query and its results are stored in the cluster only if the request does not complete during the period set by the `wait_for_completion_timeout` parameter.","x-found-in":"body"},"settings":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlQuerySettings","description":"Per-query settings, the request-body equivalent of the in-query `SET` command.\nFor example, `time_zone` can be supplied here instead of as a top-level field.","x-found-in":"body"}},"required":["query"],"description":"Run an async ES|QL query.\n\nAsynchronously run an ES|QL (Elasticsearch query language) query, monitor its progress, and retrieve results when they become available.\n\nThe API accepts the same parameters and request body as the synchronous query API, along with additional async related properties."}

package/src/es/json/esql.query.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"esql.query","type":"object","properties":{"columnar":{"type":"boolean","description":"By default, ES|QL returns results as rows. For example, FROM returns each individual document as one row. For the JSON, YAML, CBOR and smile formats, ES|QL can return the results in a columnar fashion where one row represents all the values of a certain column in the results.","x-found-in":"body"},"filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Specify a Query DSL query in the filter parameter to filter the set of documents that an ES|QL query runs on.","x-found-in":"body"},"time_zone":{"type":"string","description":"Sets the default timezone of the query.","x-found-in":"body"},"locale":{"type":"string","description":"Returns results (especially dates) formatted per the conventions of the locale.","x-found-in":"body"},"params":{"$ref":"./esql._types.json#/$defs/esql._types__ESQLParams","description":"To avoid any attempts of hacking or code injection, extract the values in a separate list of parameters. Use question mark placeholders (?) in the query string for each of the parameters.","x-found-in":"body"},"profile":{"type":"boolean","description":"If provided and `true` the response will include an extra `profile` object\nwith information on how the query was executed. This information is for human debugging\nand its format can change at any time but it can give some insight into the performance\nof each part of the query.","x-found-in":"body"},"query":{"type":"string","description":"The ES|QL query API accepts an ES|QL query string in the query parameter, runs it, and returns the results.","x-found-in":"body"},"tables":{"type":"object","additionalProperties":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesContainer"}},"description":"Tables to use with the LOOKUP operation. The top level key is the table\nname and the next level key is the column name.","x-found-in":"body"},"include_ccs_metadata":{"type":"boolean","description":"When set to `true` and performing a cross-cluster/cross-project query, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.","x-found-in":"body"},"include_execution_metadata":{"type":"boolean","description":"When set to `true`, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.\nThis is similar to `include_ccs_metadata`, but it also returns metadata when the query is not CCS/CPS","x-found-in":"body"},"settings":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlQuerySettings","description":"Per-query settings, the request-body equivalent of the in-query `SET` command.\nFor example, `time_zone` can be supplied here instead of as a top-level field.","x-found-in":"body"},"format":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlFormat","description":"A short version of the Accept header, e.g. json, yaml.\n\n`csv`, `tsv`, and `txt` formats will return results in a tabular format, excluding other metadata fields from the response.","x-found-in":"query"},"delimiter":{"type":"string","description":"The character to use between values within a CSV row. Only valid for the CSV format.","x-found-in":"query"},"drop_null_columns":{"type":"boolean","description":"Should columns that are entirely `null` be removed from the `columns` and `values` portion of the results?\nDefaults to `false`. If `true` then the response will include an extra section under the name `all_columns` which has the name of all columns.","x-found-in":"query"},"allow_partial_results":{"type":"boolean","description":"If `true`, partial results will be returned if there are shard failures, but the query can continue to execute on other clusters and shards.\nIf `false`, the query will fail if there are any failures.\n\nTo override the default behavior, you can set the `esql.query.allow_partial_results` cluster setting to `false`.","x-found-in":"query"}},"required":["query"],"description":"Run an ES|QL query.\n\nGet search results for an ES|QL (Elasticsearch query language) query."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"esql.query","type":"object","properties":{"format":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlFormat","description":"A short version of the Accept header, e.g. json, yaml.\n\n`csv`, `tsv`, and `txt` formats will return results in a tabular format, excluding other metadata fields from the response.","x-found-in":"query"},"delimiter":{"type":"string","description":"The character to use between values within a CSV row. Only valid for the CSV format.","x-found-in":"query"},"drop_null_columns":{"type":"boolean","description":"Should columns that are entirely `null` be removed from the `columns` and `values` portion of the results?\nDefaults to `false`. If `true` then the response will include an extra section under the name `all_columns` which has the name of all columns.","x-found-in":"query"},"allow_partial_results":{"type":"boolean","description":"If `true`, partial results will be returned if there are shard failures, but the query can continue to execute on other clusters and shards.\nIf `false`, the query will fail if there are any failures.\n\nTo override the default behavior, you can set the `esql.query.allow_partial_results` cluster setting to `false`.","x-found-in":"query"},"columnar":{"type":"boolean","description":"By default, ES|QL returns results as rows. For example, FROM returns each individual document as one row. For the JSON, YAML, CBOR and smile formats, ES|QL can return the results in a columnar fashion where one row represents all the values of a certain column in the results.","x-found-in":"body"},"filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Specify a Query DSL query in the filter parameter to filter the set of documents that an ES|QL query runs on.","x-found-in":"body"},"time_zone":{"type":"string","description":"Sets the default timezone of the query.","x-found-in":"body"},"locale":{"type":"string","description":"Returns results (especially dates) formatted per the conventions of the locale.","x-found-in":"body"},"params":{"$ref":"./esql._types.json#/$defs/esql._types__ESQLParams","description":"To avoid any attempts of hacking or code injection, extract the values in a separate list of parameters. Use question mark placeholders (?) in the query string for each of the parameters.","x-found-in":"body"},"profile":{"type":"boolean","description":"If provided and `true` the response will include an extra `profile` object\nwith information on how the query was executed. This information is for human debugging\nand its format can change at any time but it can give some insight into the performance\nof each part of the query.","x-found-in":"body"},"query":{"type":"string","description":"The ES|QL query API accepts an ES|QL query string in the query parameter, runs it, and returns the results.","x-found-in":"body"},"tables":{"type":"object","additionalProperties":{"type":"object","additionalProperties":{"$ref":"./esql._types.json#/$defs/esql._types__TableValuesContainer"}},"description":"Tables to use with the LOOKUP operation. The top level key is the table\nname and the next level key is the column name.","x-found-in":"body"},"include_ccs_metadata":{"type":"boolean","description":"When set to `true` and performing a cross-cluster/cross-project query, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.","x-found-in":"body"},"include_execution_metadata":{"type":"boolean","description":"When set to `true`, the response will include an extra `_clusters`\nobject with information about the clusters that participated in the search along with info such as shards\ncount.\nThis is similar to `include_ccs_metadata`, but it also returns metadata when the query is not CCS/CPS","x-found-in":"body"},"settings":{"$ref":"./esql._types.json#/$defs/esql._types__EsqlQuerySettings","description":"Per-query settings, the request-body equivalent of the in-query `SET` command.\nFor example, `time_zone` can be supplied here instead of as a top-level field.","x-found-in":"body"}},"required":["query"],"description":"Run an ES|QL query.\n\nGet search results for an ES|QL (Elasticsearch query language) query."}

package/src/es/json/explain.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"explain","type":"object","properties":{"query":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Defines the search definition using the Query DSL.","x-found-in":"body"},"analyzer":{"type":"string","description":"The analyzer to use for the query string.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"analyze_wildcard":{"type":"boolean","description":"If `true`, wildcard and prefix queries are analyzed.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"default_operator":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__Operator","description":"The default operator for query string query: `and` or `or`.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"df":{"type":"string","description":"The field to use as default where no field prefix is given in the query string.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"lenient":{"type":"boolean","description":"If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"preference":{"type":"string","description":"The node or shard the operation should be performed on.\nIt is random by default.","x-found-in":"query"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","description":"A custom value used to route operations to a specific shard.\nNot allowed when `index.slice.enabled` is `true` for the target index; use `_slice` instead.","x-found-in":"query"},"_source":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__SourceConfigParam","description":"`True` or `false` to return the `_source` field or not or a list of fields to return.","x-found-in":"query"},"_source_excludes":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of source fields to exclude from the response.\nYou can also use this parameter to exclude fields from the subset specified in `_source_includes` query parameter.\nIf the `_source` parameter is `false`, this parameter is ignored.","x-found-in":"query"},"_source_includes":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of source fields to include in the response.\nIf this parameter is specified, only these source fields are returned.\nYou can exclude fields from this subset using the `_source_excludes` query parameter.\nIf the `_source` parameter is `false`, this parameter is ignored.","x-found-in":"query"},"stored_fields":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of stored fields to return in the response.","x-found-in":"query"},"q":{"type":"string","description":"The query in the Lucene query string syntax.","x-found-in":"query"},"id":{"type":"string","description":"The document identifier.","x-found-in":"path"},"index":{"type":"string","description":"Index names that are used to limit the request.\nOnly a single index name can be provided to this parameter.","x-found-in":"path"}},"required":["id","index"],"description":"Explain a document match result.\n\nGet information about why a specific document matches, or doesn't match, a query.\nIt computes a score explanation for a query and a specific document."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"explain","type":"object","properties":{"analyzer":{"type":"string","description":"The analyzer to use for the query string.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"analyze_wildcard":{"type":"boolean","description":"If `true`, wildcard and prefix queries are analyzed.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"default_operator":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__Operator","description":"The default operator for query string query: `and` or `or`.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"df":{"type":"string","description":"The field to use as default where no field prefix is given in the query string.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"lenient":{"type":"boolean","description":"If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored.\nThis parameter can be used only when the `q` query string parameter is specified.","x-found-in":"query"},"preference":{"type":"string","description":"The node or shard the operation should be performed on.\nIt is random by default.","x-found-in":"query"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","description":"A custom value used to route operations to a specific shard.\nNot allowed when `index.slice.enabled` is `true` for the target index; use `_slice` instead.","x-found-in":"query"},"_source":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__SourceConfigParam","description":"`True` or `false` to return the `_source` field or not or a list of fields to return.","x-found-in":"query"},"_source_excludes":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of source fields to exclude from the response.\nYou can also use this parameter to exclude fields from the subset specified in `_source_includes` query parameter.\nIf the `_source` parameter is `false`, this parameter is ignored.","x-found-in":"query"},"_source_includes":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of source fields to include in the response.\nIf this parameter is specified, only these source fields are returned.\nYou can exclude fields from this subset using the `_source_excludes` query parameter.\nIf the `_source` parameter is `false`, this parameter is ignored.","x-found-in":"query"},"stored_fields":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of stored fields to return in the response.","x-found-in":"query"},"q":{"type":"string","description":"The query in the Lucene query string syntax.","x-found-in":"query"},"query":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Defines the search definition using the Query DSL.","x-found-in":"body"},"id":{"type":"string","description":"The document identifier.","x-found-in":"path"},"index":{"type":"string","description":"Index names that are used to limit the request.\nOnly a single index name can be provided to this parameter.","x-found-in":"path"}},"required":["id","index"],"description":"Explain a document match result.\n\nGet information about why a specific document matches, or doesn't match, a query.\nIt computes a score explanation for a query and a specific document."}

package/src/es/json/field_caps.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"field_caps","type":"object","properties":{"fields":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A comma-separated list of fields to retrieve capabilities for. Wildcard (`*`) expressions are supported.","x-found-in":"query"},"index_filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Filter indices if the provided query rewrites to `match_none` on every shard.\n\nIMPORTANT: The filtering is done on a best-effort basis, it uses index statistics and mappings to rewrite queries to `match_none` instead of fully running the request.\nFor instance a range query over a date field can rewrite to `match_none` if all documents within a shard (including deleted documents) are outside of the provided range.\nHowever, not all queries can rewrite to `match_none` so this API may return an index even if the provided filter matches no document.","x-found-in":"body"},"runtime_mappings":{"$ref":"./_types.mapping.json#/$defs/_types.mapping__RuntimeFields","description":"Define ad-hoc runtime fields in the request similar to the way it is done in search requests.\nThese fields exist only as part of the query and take precedence over fields defined with the same name in the index mappings.","x-found-in":"body"},"allow_no_indices":{"type":"boolean","description":"A setting that does two separate checks on the index expression.\nIf `false`, the request returns an error (1) if any wildcard expression\n(including `_all` and `*`) resolves to zero matching indices or (2) if the\ncomplete set of resolved indices, aliases or data streams is empty after all\nexpressions are evaluated. If `true`, index expressions that resolve to no\nindices are allowed and the request returns an empty result.","x-found-in":"query"},"expand_wildcards":{"$ref":"./_types.json#/$defs/_types__ExpandWildcards","description":"The type of index that wildcard patterns can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. Supports comma-separated values, such as `open,hidden`.","x-found-in":"query"},"ignore_unavailable":{"type":"boolean","description":"If `false`, the request returns an error if it targets a concrete (non-wildcarded)\nindex, alias, or data stream that is missing, closed, or otherwise unavailable.\nIf `true`, unavailable concrete targets are silently ignored.","x-found-in":"query"},"include_unmapped":{"type":"boolean","description":"If true, unmapped fields are included in the response.","x-found-in":"query"},"filters":{"oneOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"A comma-separated list of filters to apply to the response.","x-found-in":"query"},"types":{"type":"array","items":{"type":"string"},"description":"A comma-separated list of field types to include.\nAny fields that do not match one of these types will be excluded from the results.\nIt defaults to empty, meaning that all field types are returned.","x-found-in":"query"},"include_empty_fields":{"type":"boolean","description":"If false, empty fields are not included in the response.","x-found-in":"query"},"index":{"$ref":"./_types.json#/$defs/_types__Indices","description":"A comma-separated list of data streams, indices, and aliases used to limit the request. Supports wildcards (*). To target all data streams and indices, omit this parameter or use * or _all.","x-found-in":"path"}},"description":"Get the field capabilities.\n\nGet information about the capabilities of fields among multiple indices.\n\nFor data streams, the API returns field capabilities among the stream’s backing indices.\nIt returns runtime fields like any other field.\nFor example, a runtime field with a type of keyword is returned the same as any other field that belongs to the `keyword` family."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"field_caps","type":"object","properties":{"allow_no_indices":{"type":"boolean","description":"A setting that does two separate checks on the index expression.\nIf `false`, the request returns an error (1) if any wildcard expression\n(including `_all` and `*`) resolves to zero matching indices or (2) if the\ncomplete set of resolved indices, aliases or data streams is empty after all\nexpressions are evaluated. If `true`, index expressions that resolve to no\nindices are allowed and the request returns an empty result.","x-found-in":"query"},"expand_wildcards":{"$ref":"./_types.json#/$defs/_types__ExpandWildcards","description":"The type of index that wildcard patterns can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. Supports comma-separated values, such as `open,hidden`.","x-found-in":"query"},"fields":{"$ref":"./_types.json#/$defs/_types__Fields","description":"A list of fields to retrieve capabilities for. Wildcard (`*`) expressions are supported.","x-found-in":"body"},"ignore_unavailable":{"type":"boolean","description":"If `false`, the request returns an error if it targets a concrete (non-wildcarded)\nindex, alias, or data stream that is missing, closed, or otherwise unavailable.\nIf `true`, unavailable concrete targets are silently ignored.","x-found-in":"query"},"include_unmapped":{"type":"boolean","description":"If true, unmapped fields are included in the response.","x-found-in":"query"},"filters":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"A comma-separated list of filters to apply to the response.","x-found-in":"query"},"types":{"type":"array","items":{"type":"string"},"description":"A comma-separated list of field types to include.\nAny fields that do not match one of these types will be excluded from the results.\nIt defaults to empty, meaning that all field types are returned.","x-found-in":"query"},"include_empty_fields":{"type":"boolean","description":"If false, empty fields are not included in the response.","x-found-in":"query"},"index_filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Filter indices if the provided query rewrites to `match_none` on every shard.\n\nIMPORTANT: The filtering is done on a best-effort basis, it uses index statistics and mappings to rewrite queries to `match_none` instead of fully running the request.\nFor instance a range query over a date field can rewrite to `match_none` if all documents within a shard (including deleted documents) are outside of the provided range.\nHowever, not all queries can rewrite to `match_none` so this API may return an index even if the provided filter matches no document.","x-found-in":"body"},"runtime_mappings":{"$ref":"./_types.mapping.json#/$defs/_types.mapping__RuntimeFields","description":"Define ad-hoc runtime fields in the request similar to the way it is done in search requests.\nThese fields exist only as part of the query and take precedence over fields defined with the same name in the index mappings.","x-found-in":"body"},"index":{"$ref":"./_types.json#/$defs/_types__Indices","description":"A comma-separated list of data streams, indices, and aliases used to limit the request. Supports wildcards (*). To target all data streams and indices, omit this parameter or use * or _all.","x-found-in":"path"}},"description":"Get the field capabilities.\n\nGet information about the capabilities of fields among multiple indices.\n\nFor data streams, the API returns field capabilities among the stream’s backing indices.\nIt returns runtime fields like any other field.\nFor example, a runtime field with a type of keyword is returned the same as any other field that belongs to the `keyword` family."}

package/src/es/json/fleet.global_checkpoints.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"fleet.global_checkpoints","type":"object","properties":{"wait_for_advance":{"type":"boolean","description":"A boolean value which controls whether to wait (until the timeout) for the global checkpoints\nto advance past the provided `checkpoints`.","x-found-in":"query"},"wait_for_index":{"type":"boolean","description":"A boolean value which controls whether to wait (until the timeout) for the target index to exist\nand all primary shards be active. Can only be true when `wait_for_advance` is true.","x-found-in":"query"},"checkpoints":{"type":"array","items":{"type":"number"},"description":"A comma separated list of previous global checkpoints. When used in combination with `wait_for_advance`,\nthe API will only return once the global checkpoints advances past the checkpoints. Providing an empty list\nwill cause Elasticsearch to immediately return the current global checkpoints.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Period to wait for a global checkpoints to advance past `checkpoints`.","x-found-in":"query"},"index":{"oneOf":[{"type":"string"},{"type":"string"}],"description":"A single index or index alias that resolves to a single index.","x-found-in":"path"}},"required":["index"],"description":"Get global checkpoints.\n\nGet the current global checkpoints for an index.\nThis API is designed for internal use by the Fleet server project."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"fleet.global_checkpoints","type":"object","properties":{"wait_for_advance":{"type":"boolean","description":"A boolean value which controls whether to wait (until the timeout) for the global checkpoints\nto advance past the provided `checkpoints`.","x-found-in":"query"},"wait_for_index":{"type":"boolean","description":"A boolean value which controls whether to wait (until the timeout) for the target index to exist\nand all primary shards be active. Can only be true when `wait_for_advance` is true.","x-found-in":"query"},"checkpoints":{"type":"array","items":{"type":"number"},"description":"A comma separated list of previous global checkpoints. When used in combination with `wait_for_advance`,\nthe API will only return once the global checkpoints advances past the checkpoints. Providing an empty list\nwill cause Elasticsearch to immediately return the current global checkpoints.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Period to wait for a global checkpoints to advance past `checkpoints`.","x-found-in":"query"},"index":{"anyOf":[{"type":"string"},{"type":"string"}],"description":"A single index or index alias that resolves to a single index.","x-found-in":"path"}},"required":["index"],"description":"Get global checkpoints.\n\nGet the current global checkpoints for an index.\nThis API is designed for internal use by the Fleet server project."}

package/src/es/json/fleet.msearch.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"fleet.msearch","type":"object","properties":{"allow_no_indices":{"type":"boolean","description":"A setting that does two separate checks on the index expression.\nIf `false`, the request returns an error (1) if any wildcard expression\n(including `_all` and `*`) resolves to zero matching indices or (2) if the\ncomplete set of resolved indices, aliases or data streams is empty after all\nexpressions are evaluated. If `true`, index expressions that resolve to no\nindices are allowed and the request returns an empty result.","x-found-in":"query"},"ccs_minimize_roundtrips":{"type":"boolean","description":"If true, network roundtrips between the coordinating node and remote clusters are minimized for cross-cluster search requests.","x-found-in":"query"},"expand_wildcards":{"$ref":"./_types.json#/$defs/_types__ExpandWildcards","description":"Type of index that wildcard expressions can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams.","x-found-in":"query"},"ignore_throttled":{"type":"boolean","description":"If true, concrete, expanded or aliased indices are ignored when frozen.","x-found-in":"query"},"ignore_unavailable":{"type":"boolean","description":"If `false`, the request returns an error if it targets a concrete (non-wildcarded)\nindex, alias, or data stream that is missing, closed, or otherwise unavailable.\nIf `true`, unavailable concrete targets are silently ignored.","x-found-in":"query"},"max_concurrent_searches":{"type":"number","description":"Maximum number of concurrent searches the multi search API can execute.","x-found-in":"query"},"max_concurrent_shard_requests":{"type":"number","description":"Maximum number of concurrent shard requests that each sub-search request executes per node.","x-found-in":"query"},"pre_filter_shard_size":{"type":"number","description":"Defines a threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold. This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on its rewrite method i.e., if date filters are mandatory to match but the shard bounds and the query are disjoint.","x-found-in":"query"},"search_type":{"$ref":"./_types.json#/$defs/_types__SearchType","description":"Indicates whether global term and document frequencies should be used when scoring returned documents.","x-found-in":"query"},"rest_total_hits_as_int":{"type":"boolean","description":"If true, hits.total are returned as an integer in the response. Defaults to false, which returns an object.","x-found-in":"query"},"typed_keys":{"type":"boolean","description":"Specifies whether aggregation and suggester names should be prefixed by their respective types in the response.","x-found-in":"query"},"wait_for_checkpoints":{"type":"array","items":{"type":"number"},"description":"A comma separated list of checkpoints. When configured, the search API will only be executed on a shard\nafter the relevant checkpoint has become visible for search. Defaults to an empty list which will cause\nElasticsearch to immediately execute the search.","x-found-in":"query"},"allow_partial_search_results":{"type":"boolean","description":"If true, returns partial results if there are shard request timeouts or shard failures.\nIf false, returns an error with no partial results.\nDefaults to the configured cluster setting `search.default_allow_partial_results`, which is true by default.","x-found-in":"query"},"index":{"oneOf":[{"type":"string"},{"type":"string"}],"description":"A single target to search. If the target is an index alias, it must resolve to a single index.","x-found-in":"path"}},"description":"Run multiple Fleet searches.\n\nRun several Fleet searches with a single API request.\nThe API follows the same structure as the multi search API.\nHowever, similar to the Fleet search API, it supports the `wait_for_checkpoints` parameter."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"fleet.msearch","type":"object","properties":{"allow_no_indices":{"type":"boolean","description":"A setting that does two separate checks on the index expression.\nIf `false`, the request returns an error (1) if any wildcard expression\n(including `_all` and `*`) resolves to zero matching indices or (2) if the\ncomplete set of resolved indices, aliases or data streams is empty after all\nexpressions are evaluated. If `true`, index expressions that resolve to no\nindices are allowed and the request returns an empty result.","x-found-in":"query"},"ccs_minimize_roundtrips":{"type":"boolean","description":"If true, network roundtrips between the coordinating node and remote clusters are minimized for cross-cluster search requests.","x-found-in":"query"},"expand_wildcards":{"$ref":"./_types.json#/$defs/_types__ExpandWildcards","description":"Type of index that wildcard expressions can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams.","x-found-in":"query"},"ignore_throttled":{"type":"boolean","description":"If true, concrete, expanded or aliased indices are ignored when frozen.","x-found-in":"query"},"ignore_unavailable":{"type":"boolean","description":"If `false`, the request returns an error if it targets a concrete (non-wildcarded)\nindex, alias, or data stream that is missing, closed, or otherwise unavailable.\nIf `true`, unavailable concrete targets are silently ignored.","x-found-in":"query"},"max_concurrent_searches":{"type":"number","description":"Maximum number of concurrent searches the multi search API can execute.","x-found-in":"query"},"max_concurrent_shard_requests":{"type":"number","description":"Maximum number of concurrent shard requests that each sub-search request executes per node.","x-found-in":"query"},"pre_filter_shard_size":{"type":"number","description":"Defines a threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold. This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on its rewrite method i.e., if date filters are mandatory to match but the shard bounds and the query are disjoint.","x-found-in":"query"},"search_type":{"$ref":"./_types.json#/$defs/_types__SearchType","description":"Indicates whether global term and document frequencies should be used when scoring returned documents.","x-found-in":"query"},"rest_total_hits_as_int":{"type":"boolean","description":"If true, hits.total are returned as an integer in the response. Defaults to false, which returns an object.","x-found-in":"query"},"typed_keys":{"type":"boolean","description":"Specifies whether aggregation and suggester names should be prefixed by their respective types in the response.","x-found-in":"query"},"wait_for_checkpoints":{"type":"array","items":{"type":"number"},"description":"A comma separated list of checkpoints. When configured, the search API will only be executed on a shard\nafter the relevant checkpoint has become visible for search. Defaults to an empty list which will cause\nElasticsearch to immediately execute the search.","x-found-in":"query"},"allow_partial_search_results":{"type":"boolean","description":"If true, returns partial results if there are shard request timeouts or shard failures.\nIf false, returns an error with no partial results.\nDefaults to the configured cluster setting `search.default_allow_partial_results`, which is true by default.","x-found-in":"query"},"searches":{"type":"array","items":{"$ref":"./_global.msearch.json#/$defs/_global.msearch__RequestItem"},"x-found-in":"body"},"index":{"anyOf":[{"type":"string"},{"type":"string"}],"description":"A single target to search. If the target is an index alias, it must resolve to a single index.","x-found-in":"path"}},"description":"Run multiple Fleet searches.\n\nRun several Fleet searches with a single API request.\nThe API follows the same structure as the multi search API.\nHowever, similar to the Fleet search API, it supports the `wait_for_checkpoints` parameter."}

package/src/es/json/fleet.search.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"fleet.search","type":"object","properties":{"aggregations":{"type":"object","additionalProperties":{"$ref":"./_types.aggregations.json#/$defs/_types.aggregations__AggregationContainer"},"x-found-in":"body"},"collapse":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__FieldCollapse","x-found-in":"body"},"explain":{"type":"boolean","x-found-in":"query"},"ext":{"type":"object","additionalProperties":{},"description":"Configuration of search extensions defined by Elasticsearch plugins.","x-found-in":"body"},"from":{"type":"number","x-found-in":"query"},"highlight":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Highlight","x-found-in":"body"},"track_total_hits":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__TrackHits","x-found-in":"query"},"indices_boost":{"type":"array","items":{"type":"object","additionalProperties":{"type":"number"}},"description":"Boosts the _score of documents from specified indices.","x-found-in":"body"},"docvalue_fields":{"$ref":"./_types.json#/$defs/_types__Fields","x-found-in":"query"},"min_score":{"type":"number","description":"Minimum _score for matching documents. Documents with a lower _score are\nnot included in search results and results collected by aggregations.","x-found-in":"body"},"post_filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","x-found-in":"body"},"profile":{"type":"boolean","x-found-in":"body"},"query":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Defines the search definition using the Query DSL.","x-found-in":"body"},"rescore":{"oneOf":[{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Rescore"},{"type":"array","items":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Rescore"}}],"x-found-in":"body"},"script_fields":{"type":"object","additionalProperties":{"$ref":"./_types.json#/$defs/_types__ScriptField"},"description":"Retrieve a script evaluation (based on different fields) for each hit.","x-found-in":"body"},"search_after":{"$ref":"./_types.json#/$defs/_types__SortResults","x-found-in":"body"},"size":{"type":"number","x-found-in":"query"},"slice":{"$ref":"./_types.json#/$defs/_types__SlicedScroll","x-found-in":"body"},"sort":{"oneOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"x-found-in":"query"},"_source":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__SourceConfigParam","x-found-in":"query"},"fields":{"type":"array","items":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__FieldAndFormat"},"description":"Array of wildcard (*) patterns. The request returns values for field names\nmatching these patterns in the hits.fields property of the response.","x-found-in":"body"},"suggest":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Suggester","x-found-in":"body"},"terminate_after":{"type":"number","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","x-found-in":"query"},"track_scores":{"type":"boolean","x-found-in":"query"},"version":{"type":"boolean","x-found-in":"query"},"seq_no_primary_term":{"type":"boolean","x-found-in":"query"},"stored_fields":{"$ref":"./_types.json#/$defs/_types__Fields","x-found-in":"query"},"pit":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__PointInTimeReference","description":"Limits the search to a point in time (PIT). If you provide a PIT, you\ncannot specify an <index> in the request path.","x-found-in":"body"},"runtime_mappings":{"$ref":"./_types.mapping.json#/$defs/_types.mapping__RuntimeFields","description":"Defines one or more runtime fields in the search request. These fields take\nprecedence over mapped fields with the same name.","x-found-in":"body"},"stats":{"type":"array","items":{"type":"string"},"x-found-in":"query"},"allow_no_indices":{"type":"boolean","description":"A setting that does two separate checks on the index expression.\nIf `false`, the request returns an error (1) if any wildcard expression\n(including `_all` and `*`) resolves to zero matching indices or (2) if the\ncomplete set of resolved indices, aliases or data streams is empty after all\nexpressions are evaluated. If `true`, index expressions that resolve to no\nindices are allowed and the request returns an empty result.","x-found-in":"query"},"analyzer":{"type":"string","x-found-in":"query"},"analyze_wildcard":{"type":"boolean","x-found-in":"query"},"batched_reduce_size":{"type":"number","x-found-in":"query"},"ccs_minimize_roundtrips":{"type":"boolean","x-found-in":"query"},"default_operator":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__Operator","x-found-in":"query"},"df":{"type":"string","x-found-in":"query"},"expand_wildcards":{"$ref":"./_types.json#/$defs/_types__ExpandWildcards","x-found-in":"query"},"ignore_throttled":{"type":"boolean","x-found-in":"query"},"ignore_unavailable":{"type":"boolean","description":"If `false`, the request returns an error if it targets a concrete (non-wildcarded)\nindex, alias, or data stream that is missing, closed, or otherwise unavailable.\nIf `true`, unavailable concrete targets are silently ignored.","x-found-in":"query"},"lenient":{"type":"boolean","x-found-in":"query"},"max_concurrent_shard_requests":{"type":"number","x-found-in":"query"},"preference":{"type":"string","x-found-in":"query"},"pre_filter_shard_size":{"type":"number","x-found-in":"query"},"request_cache":{"type":"boolean","x-found-in":"query"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","x-found-in":"query"},"scroll":{"$ref":"./_types.json#/$defs/_types__Duration","x-found-in":"query"},"search_type":{"$ref":"./_types.json#/$defs/_types__SearchType","x-found-in":"query"},"suggest_field":{"type":"string","description":"Specifies which field to use for suggestions.","x-found-in":"query"},"suggest_mode":{"$ref":"./_types.json#/$defs/_types__SuggestMode","x-found-in":"query"},"suggest_size":{"type":"number","x-found-in":"query"},"suggest_text":{"type":"string","description":"The source text for which the suggestions should be returned.","x-found-in":"query"},"typed_keys":{"type":"boolean","x-found-in":"query"},"rest_total_hits_as_int":{"type":"boolean","x-found-in":"query"},"_source_excludes":{"$ref":"./_types.json#/$defs/_types__Fields","x-found-in":"query"},"_source_includes":{"$ref":"./_types.json#/$defs/_types__Fields","x-found-in":"query"},"q":{"type":"string","x-found-in":"query"},"wait_for_checkpoints":{"type":"array","items":{"type":"number"},"description":"A comma separated list of checkpoints. When configured, the search API will only be executed on a shard\nafter the relevant checkpoint has become visible for search. Defaults to an empty list which will cause\nElasticsearch to immediately execute the search.","x-found-in":"query"},"allow_partial_search_results":{"type":"boolean","description":"If true, returns partial results if there are shard request timeouts or shard failures.\nIf false, returns an error with no partial results.\nDefaults to the configured cluster setting `search.default_allow_partial_results`, which is true by default.","x-found-in":"query"},"index":{"oneOf":[{"type":"string"},{"type":"string"}],"description":"A single target to search. If the target is an index alias, it must resolve to a single index.","x-found-in":"path"}},"required":["index"],"description":"Run a Fleet search.\n\nThe purpose of the Fleet search API is to provide an API where the search will be run only\nafter the provided checkpoint has been processed and is visible for searches inside of Elasticsearch."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"fleet.search","type":"object","properties":{"allow_no_indices":{"type":"boolean","description":"A setting that does two separate checks on the index expression.\nIf `false`, the request returns an error (1) if any wildcard expression\n(including `_all` and `*`) resolves to zero matching indices or (2) if the\ncomplete set of resolved indices, aliases or data streams is empty after all\nexpressions are evaluated. If `true`, index expressions that resolve to no\nindices are allowed and the request returns an empty result.","x-found-in":"query"},"analyzer":{"type":"string","x-found-in":"query"},"analyze_wildcard":{"type":"boolean","x-found-in":"query"},"batched_reduce_size":{"type":"number","x-found-in":"query"},"ccs_minimize_roundtrips":{"type":"boolean","x-found-in":"query"},"default_operator":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__Operator","x-found-in":"query"},"df":{"type":"string","x-found-in":"query"},"docvalue_fields":{"type":"array","items":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__FieldAndFormat"},"description":"Array of wildcard (*) patterns. The request returns doc values for field\nnames matching these patterns in the hits.fields property of the response.","x-found-in":"body"},"expand_wildcards":{"$ref":"./_types.json#/$defs/_types__ExpandWildcards","x-found-in":"query"},"explain":{"type":"boolean","description":"If true, returns detailed information about score computation as part of a hit.","x-found-in":"body"},"ignore_throttled":{"type":"boolean","x-found-in":"query"},"ignore_unavailable":{"type":"boolean","description":"If `false`, the request returns an error if it targets a concrete (non-wildcarded)\nindex, alias, or data stream that is missing, closed, or otherwise unavailable.\nIf `true`, unavailable concrete targets are silently ignored.","x-found-in":"query"},"lenient":{"type":"boolean","x-found-in":"query"},"max_concurrent_shard_requests":{"type":"number","x-found-in":"query"},"preference":{"type":"string","x-found-in":"query"},"pre_filter_shard_size":{"type":"number","x-found-in":"query"},"request_cache":{"type":"boolean","x-found-in":"query"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","x-found-in":"query"},"scroll":{"$ref":"./_types.json#/$defs/_types__Duration","x-found-in":"query"},"search_type":{"$ref":"./_types.json#/$defs/_types__SearchType","x-found-in":"query"},"stats":{"type":"array","items":{"type":"string"},"description":"Stats groups to associate with the search. Each group maintains a statistics\naggregation for its associated searches. You can retrieve these stats using\nthe indices stats API.","x-found-in":"body"},"stored_fields":{"$ref":"./_types.json#/$defs/_types__Fields","description":"List of stored fields to return as part of a hit. If no fields are specified,\nno stored fields are included in the response. If this field is specified, the _source\nparameter defaults to false. You can pass _source: true to return both source fields\nand stored fields in the search response.","x-found-in":"body"},"suggest_field":{"type":"string","description":"Specifies which field to use for suggestions.","x-found-in":"query"},"suggest_mode":{"$ref":"./_types.json#/$defs/_types__SuggestMode","x-found-in":"query"},"suggest_size":{"type":"number","x-found-in":"query"},"suggest_text":{"type":"string","description":"The source text for which the suggestions should be returned.","x-found-in":"query"},"terminate_after":{"type":"number","description":"Maximum number of documents to collect for each shard. If a query reaches this\nlimit, Elasticsearch terminates the query early. Elasticsearch collects documents\nbefore sorting. Defaults to 0, which does not terminate query execution early.","x-found-in":"body"},"timeout":{"type":"string","description":"Specifies the period of time to wait for a response from each shard. If no response\nis received before the timeout expires, the request fails and returns an error.\nDefaults to no timeout.","x-found-in":"body"},"track_total_hits":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__TrackHits","description":"Number of hits matching the query to count accurately. If true, the exact\nnumber of hits is returned at the cost of some performance. If false, the\nresponse does not include the total number of hits matching the query.\nDefaults to 10,000 hits.","x-found-in":"body"},"track_scores":{"type":"boolean","description":"If true, calculate and return document scores, even if the scores are not used for sorting.","x-found-in":"body"},"typed_keys":{"type":"boolean","x-found-in":"query"},"rest_total_hits_as_int":{"type":"boolean","x-found-in":"query"},"version":{"type":"boolean","description":"If true, returns document version as part of a hit.","x-found-in":"body"},"_source":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__SourceConfig","description":"Indicates which source fields are returned for matching documents. These\nfields are returned in the hits._source property of the search response.","x-found-in":"body"},"_source_excludes":{"$ref":"./_types.json#/$defs/_types__Fields","x-found-in":"query"},"_source_includes":{"$ref":"./_types.json#/$defs/_types__Fields","x-found-in":"query"},"seq_no_primary_term":{"type":"boolean","description":"If true, returns sequence number and primary term of the last modification\nof each hit. See Optimistic concurrency control.","x-found-in":"body"},"q":{"type":"string","x-found-in":"query"},"size":{"type":"number","description":"The number of hits to return. By default, you cannot page through more\nthan 10,000 hits using the from and size parameters. To page through more\nhits, use the search_after parameter.","x-found-in":"body"},"from":{"type":"number","description":"Starting document offset. By default, you cannot page through more than 10,000\nhits using the from and size parameters. To page through more hits, use the\nsearch_after parameter.","x-found-in":"body"},"sort":{"$ref":"./_types.json#/$defs/_types__Sort","x-found-in":"body"},"wait_for_checkpoints":{"type":"array","items":{"type":"number"},"description":"A comma separated list of checkpoints. When configured, the search API will only be executed on a shard\nafter the relevant checkpoint has become visible for search. Defaults to an empty list which will cause\nElasticsearch to immediately execute the search.","x-found-in":"query"},"allow_partial_search_results":{"type":"boolean","description":"If true, returns partial results if there are shard request timeouts or shard failures.\nIf false, returns an error with no partial results.\nDefaults to the configured cluster setting `search.default_allow_partial_results`, which is true by default.","x-found-in":"query"},"aggregations":{"type":"object","additionalProperties":{"$ref":"./_types.aggregations.json#/$defs/_types.aggregations__AggregationContainer"},"x-found-in":"body"},"collapse":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__FieldCollapse","x-found-in":"body"},"ext":{"type":"object","additionalProperties":{},"description":"Configuration of search extensions defined by Elasticsearch plugins.","x-found-in":"body"},"highlight":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Highlight","x-found-in":"body"},"indices_boost":{"type":"array","items":{"type":"object","additionalProperties":{"type":"number"}},"description":"Boosts the _score of documents from specified indices.","x-found-in":"body"},"min_score":{"type":"number","description":"Minimum _score for matching documents. Documents with a lower _score are\nnot included in search results and results collected by aggregations.","x-found-in":"body"},"post_filter":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","x-found-in":"body"},"profile":{"type":"boolean","x-found-in":"body"},"query":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"Defines the search definition using the Query DSL.","x-found-in":"body"},"rescore":{"anyOf":[{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Rescore"},{"type":"array","items":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Rescore"}}],"x-found-in":"body"},"script_fields":{"type":"object","additionalProperties":{"$ref":"./_types.json#/$defs/_types__ScriptField"},"description":"Retrieve a script evaluation (based on different fields) for each hit.","x-found-in":"body"},"search_after":{"$ref":"./_types.json#/$defs/_types__SortResults","x-found-in":"body"},"slice":{"$ref":"./_types.json#/$defs/_types__SlicedScroll","x-found-in":"body"},"fields":{"type":"array","items":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__FieldAndFormat"},"description":"Array of wildcard (*) patterns. The request returns values for field names\nmatching these patterns in the hits.fields property of the response.","x-found-in":"body"},"suggest":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__Suggester","x-found-in":"body"},"pit":{"$ref":"./_global.search._types.json#/$defs/_global.search._types__PointInTimeReference","description":"Limits the search to a point in time (PIT). If you provide a PIT, you\ncannot specify an <index> in the request path.","x-found-in":"body"},"runtime_mappings":{"$ref":"./_types.mapping.json#/$defs/_types.mapping__RuntimeFields","description":"Defines one or more runtime fields in the search request. These fields take\nprecedence over mapped fields with the same name.","x-found-in":"body"},"index":{"anyOf":[{"type":"string"},{"type":"string"}],"description":"A single target to search. If the target is an index alias, it must resolve to a single index.","x-found-in":"path"}},"required":["index"],"description":"Run a Fleet search.\n\nThe purpose of the Fleet search API is to provide an API where the search will be run only\nafter the provided checkpoint has been processed and is visible for searches inside of Elasticsearch."}

package/src/es/json/graph.explore.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"graph.explore","type":"object","properties":{"connections":{"$ref":"./graph._types.json#/$defs/graph._types__Hop","description":"Specifies or more fields from which you want to extract terms that are associated with the specified vertices.","x-found-in":"body"},"controls":{"$ref":"./graph._types.json#/$defs/graph._types__ExploreControls","description":"Direct the Graph API how to build the graph.","x-found-in":"body"},"query":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"A seed query that identifies the documents of interest. Can be any valid Elasticsearch query.","x-found-in":"body"},"vertices":{"type":"array","items":{"$ref":"./graph._types.json#/$defs/graph._types__VertexDefinition"},"description":"Specifies one or more fields that contain the terms you want to include in the graph as vertices.","x-found-in":"body"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","description":"Custom value used to route operations to a specific shard.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Specifies the period of time to wait for a response from each shard.\nIf no response is received before the timeout expires, the request fails and returns an error.\nDefaults to no timeout.","x-found-in":"query"},"index":{"$ref":"./_types.json#/$defs/_types__Indices","description":"Name of the index.","x-found-in":"path"}},"required":["index"],"description":"Explore graph analytics.\n\nExtract and summarize information about the documents and terms in an Elasticsearch data stream or index.\nThe easiest way to understand the behavior of this API is to use the Graph UI to explore connections.\nAn initial request to the `_explore` API contains a seed query that identifies the documents of interest and specifies the fields that define the vertices and connections you want to include in the graph.\nSubsequent requests enable you to spider out from one more vertices of interest.\nYou can exclude vertices that have already been returned."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"graph.explore","type":"object","properties":{"routing":{"$ref":"./_types.json#/$defs/_types__Routing","description":"Custom value used to route operations to a specific shard.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Specifies the period of time to wait for a response from each shard.\nIf no response is received before the timeout expires, the request fails and returns an error.\nDefaults to no timeout.","x-found-in":"query"},"connections":{"$ref":"./graph._types.json#/$defs/graph._types__Hop","description":"Specifies or more fields from which you want to extract terms that are associated with the specified vertices.","x-found-in":"body"},"controls":{"$ref":"./graph._types.json#/$defs/graph._types__ExploreControls","description":"Direct the Graph API how to build the graph.","x-found-in":"body"},"query":{"$ref":"./_types.query_dsl.json#/$defs/_types.query_dsl__QueryContainer","description":"A seed query that identifies the documents of interest. Can be any valid Elasticsearch query.","x-found-in":"body"},"vertices":{"type":"array","items":{"$ref":"./graph._types.json#/$defs/graph._types__VertexDefinition"},"description":"Specifies one or more fields that contain the terms you want to include in the graph as vertices.","x-found-in":"body"},"index":{"$ref":"./_types.json#/$defs/_types__Indices","description":"Name of the index.","x-found-in":"path"}},"required":["index"],"description":"Explore graph analytics.\n\nExtract and summarize information about the documents and terms in an Elasticsearch data stream or index.\nThe easiest way to understand the behavior of this API is to use the Graph UI to explore connections.\nAn initial request to the `_explore` API contains a seed query that identifies the documents of interest and specifies the fields that define the vertices and connections you want to include in the graph.\nSubsequent requests enable you to spider out from one more vertices of interest.\nYou can exclude vertices that have already been returned."}

package/src/es/json/health_report.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"health_report","type":"object","properties":{"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Explicit operation timeout.","x-found-in":"query"},"verbose":{"type":"boolean","description":"Opt-in for more information about the health of the system.","x-found-in":"query"},"size":{"type":"number","description":"Limit the number of affected resources the health report API returns.","x-found-in":"query"},"feature":{"oneOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"A feature of the cluster, as returned by the top-level health report API.","x-found-in":"path"}},"description":"Get the cluster health.\n\nGet a report with the health status of an Elasticsearch cluster.\nThe report contains a list of indicators that compose Elasticsearch functionality.\n\nEach indicator has a health status of: green, unknown, yellow or red.\nThe indicator will provide an explanation and metadata describing the reason for its current health status.\n\nThe cluster’s status is controlled by the worst indicator status.\n\nIn the event that an indicator’s status is non-green, a list of impacts may be present in the indicator result which detail the functionalities that are negatively affected by the health issue.\nEach impact carries with it a severity level, an area of the system that is affected, and a simple description of the impact on the system.\n\nSome health indicators can determine the root cause of a health problem and prescribe a set of steps that can be performed in order to improve the health of the system.\nThe root cause and remediation steps are encapsulated in a diagnosis.\nA diagnosis contains a cause detailing a root cause analysis, an action containing a brief description of the steps to take to fix the problem, the list of affected resources (if applicable), and a detailed step-by-step troubleshooting guide to fix the diagnosed problem.\n\nNOTE: The health indicators perform root cause analysis of non-green health statuses. This can be computationally expensive when called frequently.\nWhen setting up automated polling of the API for health status, set verbose to false to disable the more expensive analysis logic."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"health_report","type":"object","properties":{"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Explicit operation timeout.","x-found-in":"query"},"verbose":{"type":"boolean","description":"Opt-in for more information about the health of the system.","x-found-in":"query"},"size":{"type":"number","description":"Limit the number of affected resources the health report API returns.","x-found-in":"query"},"feature":{"anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}],"description":"A feature of the cluster, as returned by the top-level health report API.","x-found-in":"path"}},"description":"Get the cluster health.\n\nGet a report with the health status of an Elasticsearch cluster.\nThe report contains a list of indicators that compose Elasticsearch functionality.\n\nEach indicator has a health status of: green, unknown, yellow or red.\nThe indicator will provide an explanation and metadata describing the reason for its current health status.\n\nThe cluster’s status is controlled by the worst indicator status.\n\nIn the event that an indicator’s status is non-green, a list of impacts may be present in the indicator result which detail the functionalities that are negatively affected by the health issue.\nEach impact carries with it a severity level, an area of the system that is affected, and a simple description of the impact on the system.\n\nSome health indicators can determine the root cause of a health problem and prescribe a set of steps that can be performed in order to improve the health of the system.\nThe root cause and remediation steps are encapsulated in a diagnosis.\nA diagnosis contains a cause detailing a root cause analysis, an action containing a brief description of the steps to take to fix the problem, the list of affected resources (if applicable), and a detailed step-by-step troubleshooting guide to fix the diagnosed problem.\n\nNOTE: The health indicators perform root cause analysis of non-green health statuses. This can be computationally expensive when called frequently.\nWhen setting up automated polling of the API for health status, set verbose to false to disable the more expensive analysis logic."}

package/src/es/json/ilm.explain_lifecycle.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"ilm.explain_lifecycle__LifecycleExplain":{"oneOf":[{"$ref":"./ilm.explain_lifecycle.json#/$defs/ilm.explain_lifecycle__LifecycleExplainManaged"},{"$ref":"./ilm.explain_lifecycle.json#/$defs/ilm.explain_lifecycle__LifecycleExplainUnmanaged"}]},"ilm.explain_lifecycle__LifecycleExplainManaged":{"type":"object","properties":{"action":{"type":"string"},"action_time":{"$ref":"./_types.json#/$defs/_types__DateTime"},"action_time_millis":{},"age":{"$ref":"./_types.json#/$defs/_types__Duration"},"age_in_millis":{},"failed_step":{"type":"string"},"failed_step_retry_count":{"type":"number"},"index":{"type":"string"},"index_creation_date":{"$ref":"./_types.json#/$defs/_types__DateTime"},"index_creation_date_millis":{},"is_auto_retryable_error":{"type":"boolean"},"lifecycle_date":{"$ref":"./_types.json#/$defs/_types__DateTime"},"lifecycle_date_millis":{},"managed":{"const":true},"phase":{"type":"string"},"phase_time":{"$ref":"./_types.json#/$defs/_types__DateTime"},"phase_time_millis":{},"policy":{"type":"string"},"previous_step_info":{"type":"object","additionalProperties":{}},"repository_name":{"type":"string"},"snapshot_name":{"type":"string"},"shrink_index_name":{"type":"string"},"step":{"type":"string"},"step_info":{"type":"object","additionalProperties":{}},"step_time":{"$ref":"./_types.json#/$defs/_types__DateTime"},"step_time_millis":{},"phase_execution":{"$ref":"./ilm.explain_lifecycle.json#/$defs/ilm.explain_lifecycle__LifecycleExplainPhaseExecution"},"time_since_index_creation":{"$ref":"./_types.json#/$defs/_types__Duration"},"skip":{"type":"boolean"}},"required":["index","managed","skip"]},"ilm.explain_lifecycle__LifecycleExplainPhaseExecution":{"type":"object","properties":{"phase_definition":{"$ref":"./ilm._types.json#/$defs/ilm._types__Phase"},"policy":{"type":"string"},"version":{"type":"number"},"modified_date_in_millis":{}},"required":["policy","version","modified_date_in_millis"]},"ilm.explain_lifecycle__LifecycleExplainUnmanaged":{"type":"object","properties":{"index":{"type":"string"},"managed":{"const":false}},"required":["index","managed"]}}}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"ilm.explain_lifecycle__LifecycleExplain":{"anyOf":[{"$ref":"./ilm.explain_lifecycle.json#/$defs/ilm.explain_lifecycle__LifecycleExplainManaged"},{"$ref":"./ilm.explain_lifecycle.json#/$defs/ilm.explain_lifecycle__LifecycleExplainUnmanaged"}]},"ilm.explain_lifecycle__LifecycleExplainManaged":{"type":"object","properties":{"action":{"type":"string"},"action_time":{"$ref":"./_types.json#/$defs/_types__DateTime"},"action_time_millis":{},"age":{"$ref":"./_types.json#/$defs/_types__Duration"},"age_in_millis":{},"failed_step":{"type":"string"},"failed_step_retry_count":{"type":"number"},"index":{"type":"string"},"index_creation_date":{"$ref":"./_types.json#/$defs/_types__DateTime"},"index_creation_date_millis":{},"is_auto_retryable_error":{"type":"boolean"},"lifecycle_date":{"$ref":"./_types.json#/$defs/_types__DateTime"},"lifecycle_date_millis":{},"managed":{"const":true},"phase":{"type":"string"},"phase_time":{"$ref":"./_types.json#/$defs/_types__DateTime"},"phase_time_millis":{},"policy":{"type":"string"},"previous_step_info":{"type":"object","additionalProperties":{}},"repository_name":{"type":"string"},"snapshot_name":{"type":"string"},"shrink_index_name":{"type":"string"},"step":{"type":"string"},"step_info":{"type":"object","additionalProperties":{}},"step_time":{"$ref":"./_types.json#/$defs/_types__DateTime"},"step_time_millis":{},"phase_execution":{"$ref":"./ilm.explain_lifecycle.json#/$defs/ilm.explain_lifecycle__LifecycleExplainPhaseExecution"},"time_since_index_creation":{"$ref":"./_types.json#/$defs/_types__Duration"},"skip":{"type":"boolean"}},"required":["index","managed","skip"]},"ilm.explain_lifecycle__LifecycleExplainPhaseExecution":{"type":"object","properties":{"phase_definition":{"$ref":"./ilm._types.json#/$defs/ilm._types__Phase"},"policy":{"type":"string"},"version":{"type":"number"},"modified_date_in_millis":{}},"required":["policy","version","modified_date_in_millis"]},"ilm.explain_lifecycle__LifecycleExplainUnmanaged":{"type":"object","properties":{"index":{"type":"string"},"managed":{"const":false}},"required":["index","managed"]}}}

package/src/es/json/ilm.migrate_to_data_tiers.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"ilm.migrate_to_data_tiers","type":"object","properties":{"legacy_template_to_delete":{"type":"string","x-found-in":"body"},"node_attribute":{"type":"string","x-found-in":"body"},"dry_run":{"type":"boolean","description":"If true, simulates the migration from node attributes based allocation filters to data tiers, but does not perform the migration.\nThis provides a way to retrieve the indices and ILM policies that need to be migrated.","x-found-in":"query"},"master_timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period to wait for a connection to the master node.\nIf no response is received before the timeout expires, the request fails and returns an error.\nIt can also be set to `-1` to indicate that the request should never timeout.","x-found-in":"query"}},"description":"Migrate to data tiers routing.\n\nSwitch the indices, ILM policies, and legacy, composable, and component templates from using custom node attributes and attribute-based allocation filters to using data tiers.\nOptionally, delete one legacy index template.\nUsing node roles enables ILM to automatically move the indices between data tiers.\n\nMigrating away from custom node attributes routing can be manually performed.\nThis API provides an automated way of performing three out of the four manual steps listed in the migration guide:\n\n1. Stop setting the custom hot attribute on new indices.\n1. Remove custom allocation settings from existing ILM policies.\n1. Replace custom allocation settings from existing indices with the corresponding tier preference.\n\nILM must be stopped before performing the migration.\nUse the stop ILM and get ILM status APIs to wait until the reported operation mode is `STOPPED`."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"ilm.migrate_to_data_tiers","type":"object","properties":{"dry_run":{"type":"boolean","description":"If true, simulates the migration from node attributes based allocation filters to data tiers, but does not perform the migration.\nThis provides a way to retrieve the indices and ILM policies that need to be migrated.","x-found-in":"query"},"master_timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period to wait for a connection to the master node.\nIf no response is received before the timeout expires, the request fails and returns an error.\nIt can also be set to `-1` to indicate that the request should never timeout.","x-found-in":"query"},"legacy_template_to_delete":{"type":"string","x-found-in":"body"},"node_attribute":{"type":"string","x-found-in":"body"}},"description":"Migrate to data tiers routing.\n\nSwitch the indices, ILM policies, and legacy, composable, and component templates from using custom node attributes and attribute-based allocation filters to using data tiers.\nOptionally, delete one legacy index template.\nUsing node roles enables ILM to automatically move the indices between data tiers.\n\nMigrating away from custom node attributes routing can be manually performed.\nThis API provides an automated way of performing three out of the four manual steps listed in the migration guide:\n\n1. Stop setting the custom hot attribute on new indices.\n1. Remove custom allocation settings from existing ILM policies.\n1. Replace custom allocation settings from existing indices with the corresponding tier preference.\n\nILM must be stopped before performing the migration.\nUse the stop ILM and get ILM status APIs to wait until the reported operation mode is `STOPPED`."}

package/src/es/json/ilm.put_lifecycle.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"ilm.put_lifecycle","type":"object","properties":{"policy":{"type":"string","description":"Identifier for the policy.","x-found-in":"path"},"master_timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error.","x-found-in":"query"}},"required":["policy"],"description":"Create or update a lifecycle policy.\n\nIf the specified policy exists, it is replaced and the policy version is incremented.\n\nNOTE: Only the latest version of the policy is stored, you cannot revert to previous versions."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"ilm.put_lifecycle","type":"object","properties":{"master_timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error.","x-found-in":"query"},"policy":{"type":"string","description":"Identifier for the policy.","x-found-in":"path"}},"required":["policy"],"description":"Create or update a lifecycle policy.\n\nIf the specified policy exists, it is replaced and the policy version is incremented.\n\nNOTE: Only the latest version of the policy is stored, you cannot revert to previous versions."}

package/src/es/json/index.request.json

@@ -1 +1 @@
-{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"index","type":"object","properties":{"if_primary_term":{"type":"number","description":"Only perform the operation if the document has this primary term.","x-found-in":"query"},"if_seq_no":{"type":"number","description":"Only perform the operation if the document has this sequence number.","x-found-in":"query"},"include_source_on_error":{"type":"boolean","description":"True or false if to include the document source in the error message in case of parsing errors.","x-found-in":"query"},"op_type":{"$ref":"./_types.json#/$defs/_types__OpType","description":"Set to `create` to only index the document if it does not already exist (put if absent).\nIf a document with the specified `_id` already exists, the indexing operation will fail.\nThe behavior is the same as using the `<index>/_create` endpoint.\nIf a document ID is specified, this paramater defaults to `index`.\nOtherwise, it defaults to `create`.\nIf the request targets a data stream, an `op_type` of `create` is required.","x-found-in":"query"},"pipeline":{"type":"string","description":"The ID of the pipeline to use to preprocess incoming documents.\nIf the index has a default ingest pipeline specified, then setting the value to `_none` disables the default ingest pipeline for this request.\nIf a final pipeline is configured it will always run, regardless of the value of this parameter.","x-found-in":"query"},"refresh":{"$ref":"./_types.json#/$defs/_types__Refresh","description":"If `true`, Elasticsearch refreshes the affected shards to make this operation visible to search.\nIf `wait_for`, it waits for a refresh to make this operation visible to search.\nIf `false`, it does nothing with refreshes.","x-found-in":"query"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","description":"A custom value that is used to route operations to a specific shard.\nNot allowed when `index.slice.enabled` is `true` for the target index; use `_slice` instead.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period the request waits for the following operations: automatic index creation, dynamic mapping updates, waiting for active shards.\n\nThis parameter is useful for situations where the primary shard assigned to perform the operation might not be available when the operation runs.\nSome reasons for this might be that the primary shard is currently recovering from a gateway or undergoing relocation.\nBy default, the operation will wait on the primary shard to become available for at least 1 minute before failing and responding with an error.\nThe actual wait time could be longer, particularly when multiple waits occur.","x-found-in":"query"},"version":{"type":"number","description":"An explicit version number for concurrency control.\nIt must be a non-negative long number.","x-found-in":"query"},"version_type":{"$ref":"./_types.json#/$defs/_types__VersionType","description":"The version type.","x-found-in":"query"},"wait_for_active_shards":{"$ref":"./_types.json#/$defs/_types__WaitForActiveShards","description":"The number of shard copies that must be active before proceeding with the operation.\nYou can set it to `all` or any positive integer up to the total number of shards in the index (`number_of_replicas+1`).\nThe default value of `1` means it waits for each primary shard to be active.","x-found-in":"query"},"require_alias":{"type":"boolean","description":"If `true`, the destination must be an index alias.","x-found-in":"query"},"require_data_stream":{"type":"boolean","description":"If `true`, the request's actions must target a data stream (existing or to be created).","x-found-in":"query"},"id":{"type":"string","description":"A unique identifier for the document.\nTo automatically generate a document ID, use the `POST /<target>/_doc/` request format and omit this parameter.","x-found-in":"path"},"index":{"type":"string","description":"The name of the data stream or index to target.\nIf the target doesn't exist and matches the name or wildcard (`*`) pattern of an index template with a `data_stream` definition, this request creates the data stream.\nIf the target doesn't exist and doesn't match a data stream template, this request creates the index.\nYou can check for existing targets with the resolve index API.","x-found-in":"path"}},"required":["index"],"description":"Create or update a document in an index.\n\nAdd a JSON document to the specified data stream or index and make it searchable.\nIf the target is an index and the document already exists, the request updates the document and increments its version.\n\nNOTE: You cannot use this API to send update requests for existing documents in a data stream.\n\nIf the Elasticsearch security features are enabled, you must have the following index privileges for the target data stream, index, or index alias:\n\n* To add or overwrite a document using the `PUT /<target>/_doc/<_id>` request format, you must have the `create`, `index`, or `write` index privilege.\n* To add a document using the `POST /<target>/_doc/` request format, you must have the `create_doc`, `create`, `index`, or `write` index privilege.\n* To automatically create a data stream or index with this API request, you must have the `auto_configure`, `create_index`, or `manage` index privilege.\n\nAutomatic data stream creation requires a matching index template with data stream enabled.\n\nNOTE: Replica shards might not all be started when an indexing operation returns successfully.\nBy default, only the primary is required. Set `wait_for_active_shards` to change this default behavior (this parameter is not available in Elasticsearch Serverless).\n\n**Automatically create data streams and indices**\n\nIf the request's target doesn't exist and matches an index template with a `data_stream` definition, the index operation automatically creates the data stream.\n\nIf the target doesn't exist and doesn't match a data stream template, the operation automatically creates the index and applies any matching index templates.\n\nNOTE: Elasticsearch includes several built-in index templates. To avoid naming collisions with these templates, refer to index pattern documentation.\n\nIf no mapping exists, the index operation creates a dynamic mapping.\nBy default, new fields and objects are automatically added to the mapping if needed.\n\nAutomatic index creation is controlled by the `action.auto_create_index` setting.\nIf it is `true`, any index can be created automatically.\nYou can modify this setting to explicitly allow or block automatic creation of indices that match specified patterns or set it to `false` to turn off automatic index creation entirely.\nSpecify a comma-separated list of patterns you want to allow or prefix each pattern with `+` or `-` to indicate whether it should be allowed or blocked.\nWhen a list is specified, the default behaviour is to disallow.\n\nNOTE: The `action.auto_create_index` setting affects the automatic creation of indices only.\nIt does not affect the creation of data streams.\n\n**Optimistic concurrency control**\n\nIndex operations can be made conditional and only be performed if the last modification to the document was assigned the sequence number and primary term specified by the `if_seq_no` and `if_primary_term` parameters.\nIf a mismatch is detected, the operation will result in a `VersionConflictException` and a status code of `409`.\n\n**Routing**\n\nBy default, shard placement — or routing — is controlled by using a hash of the document's ID value.\nFor more explicit control, the value fed into the hash function used by the router can be directly specified on a per-operation basis using the `routing` parameter.\n\nWhen setting up explicit mapping, you can also use the `_routing` field to direct the index operation to extract the routing value from the document itself.\nThis does come at the (very minimal) cost of an additional document parsing pass.\nIf the `_routing` mapping is defined and set to be required, the index operation will fail if no routing value is provided or extracted.\n\nNOTE: Data streams do not support custom routing unless they were created with the `allow_custom_routing` setting enabled in the template.\n\n**Distributed**\n\nThe index operation is directed to the primary shard based on its route and performed on the actual node containing this shard.\nAfter the primary shard completes the operation, if needed, the update is distributed to applicable replicas.\n\n**Active shards**\n\nTo improve the resiliency of writes to the system, indexing operations can be configured to wait for a certain number of active shard copies before proceeding with the operation.\nIf the requisite number of active shard copies are not available, then the write operation must wait and retry, until either the requisite shard copies have started or a timeout occurs.\nBy default, write operations only wait for the primary shards to be active before proceeding (that is to say `wait_for_active_shards` is `1`).\nThis default can be overridden in the index settings dynamically by setting `index.write.wait_for_active_shards`.\nTo alter this behavior per operation, use the `wait_for_active_shards request` parameter (this parameter is not available in Elasticsearch Serverless).\n\nValid values are all or any positive integer up to the total number of configured copies per shard in the index (which is `number_of_replicas`+1).\nSpecifying a negative value or a number greater than the number of shard copies will throw an error.\n\nFor example, suppose you have a cluster of three nodes, A, B, and C and you create an index index with the number of replicas set to 3 (resulting in 4 shard copies, one more copy than there are nodes).\nIf you attempt an indexing operation, by default the operation will only ensure the primary copy of each shard is available before proceeding.\nThis means that even if B and C went down and A hosted the primary shard copies, the indexing operation would still proceed with only one copy of the data.\nIf `wait_for_active_shards` is set on the request to `3` (and all three nodes are up), the indexing operation will require 3 active shard copies before proceeding.\nThis requirement should be met because there are 3 active nodes in the cluster, each one holding a copy of the shard.\nHowever, if you set `wait_for_active_shards` to `all` (or to `4`, which is the same in this situation), the indexing operation will not proceed as you do not have all 4 copies of each shard active in the index.\nThe operation will timeout unless a new node is brought up in the cluster to host the fourth copy of the shard.\n\nIt is important to note that this setting greatly reduces the chances of the write operation not writing to the requisite number of shard copies, but it does not completely eliminate the possibility, because this check occurs before the write operation starts.\nAfter the write operation is underway, it is still possible for replication to fail on any number of shard copies but still succeed on the primary.\nThe `_shards` section of the API response reveals the number of shard copies on which replication succeeded and failed.\n\n**No operation (noop) updates**\n\nWhen updating a document by using this API, a new version of the document is always created even if the document hasn't changed.\nIf this isn't acceptable use the `_update` API with `detect_noop` set to `true`.\nThe `detect_noop` option isn't available on this API because it doesn’t fetch the old source and isn't able to compare it against the new source.\n\nThere isn't a definitive rule for when noop updates aren't acceptable.\nIt's a combination of lots of factors like how frequently your data source sends updates that are actually noops and how many queries per second Elasticsearch runs on the shard receiving the updates.\n\n**Versioning**\n\nEach indexed document is given a version number.\nBy default, internal versioning is used that starts at 1 and increments with each update, deletes included.\nOptionally, the version number can be set to an external value (for example, if maintained in a database).\nTo enable this functionality, `version_type` should be set to `external`.\nThe value provided must be a numeric, long value greater than or equal to 0, and less than around `9.2e+18`.\n\nNOTE: Versioning is completely real time, and is not affected by the near real time aspects of search operations.\nIf no version is provided, the operation runs without any version checks.\n\nWhen using the external version type, the system checks to see if the version number passed to the index request is greater than the version of the currently stored document.\nIf true, the document will be indexed and the new version number used.\nIf the value provided is less than or equal to the stored document's version number, a version conflict will occur and the index operation will fail. For example:\n\n```\nPUT my-index-000001/_doc/1?version=2&version_type=external\n{\n  \"user\": {\n    \"id\": \"elkbee\"\n  }\n}\n```\n\nIn this example, the operation will succeed since the supplied version of 2 is higher than the current document version of 1.\nIf the document was already updated and its version was set to 2 or higher, the indexing command will fail and result in a conflict (409 HTTP status code).\n\nA nice side effect is that there is no need to maintain strict ordering of async indexing operations run as a result of changes to a source database, as long as version numbers from the source database are used.\nEven the simple case of updating the Elasticsearch index using data from a database is simplified if external versioning is used, as only the latest version will be used if the index operations arrive out of order."}
+{"$schema":"https://json-schema.org/draft/2020-12/schema","title":"index","type":"object","properties":{"if_primary_term":{"type":"number","description":"Only perform the operation if the document has this primary term.","x-found-in":"query"},"if_seq_no":{"type":"number","description":"Only perform the operation if the document has this sequence number.","x-found-in":"query"},"include_source_on_error":{"type":"boolean","description":"True or false if to include the document source in the error message in case of parsing errors.","x-found-in":"query"},"op_type":{"$ref":"./_types.json#/$defs/_types__OpType","description":"Set to `create` to only index the document if it does not already exist (put if absent).\nIf a document with the specified `_id` already exists, the indexing operation will fail.\nThe behavior is the same as using the `<index>/_create` endpoint.\nIf a document ID is specified, this paramater defaults to `index`.\nOtherwise, it defaults to `create`.\nIf the request targets a data stream, an `op_type` of `create` is required.","x-found-in":"query"},"pipeline":{"type":"string","description":"The ID of the pipeline to use to preprocess incoming documents.\nIf the index has a default ingest pipeline specified, then setting the value to `_none` disables the default ingest pipeline for this request.\nIf a final pipeline is configured it will always run, regardless of the value of this parameter.","x-found-in":"query"},"refresh":{"$ref":"./_types.json#/$defs/_types__Refresh","description":"If `true`, Elasticsearch refreshes the affected shards to make this operation visible to search.\nIf `wait_for`, it waits for a refresh to make this operation visible to search.\nIf `false`, it does nothing with refreshes.","x-found-in":"query"},"routing":{"$ref":"./_types.json#/$defs/_types__Routing","description":"A custom value that is used to route operations to a specific shard.\nNot allowed when `index.slice.enabled` is `true` for the target index; use `_slice` instead.","x-found-in":"query"},"timeout":{"$ref":"./_types.json#/$defs/_types__Duration","description":"The period the request waits for the following operations: automatic index creation, dynamic mapping updates, waiting for active shards.\n\nThis parameter is useful for situations where the primary shard assigned to perform the operation might not be available when the operation runs.\nSome reasons for this might be that the primary shard is currently recovering from a gateway or undergoing relocation.\nBy default, the operation will wait on the primary shard to become available for at least 1 minute before failing and responding with an error.\nThe actual wait time could be longer, particularly when multiple waits occur.","x-found-in":"query"},"version":{"type":"number","description":"An explicit version number for concurrency control.\nIt must be a non-negative long number.","x-found-in":"query"},"version_type":{"$ref":"./_types.json#/$defs/_types__VersionType","description":"The version type.","x-found-in":"query"},"wait_for_active_shards":{"$ref":"./_types.json#/$defs/_types__WaitForActiveShards","description":"The number of shard copies that must be active before proceeding with the operation.\nYou can set it to `all` or any positive integer up to the total number of shards in the index (`number_of_replicas+1`).\nThe default value of `1` means it waits for each primary shard to be active.","x-found-in":"query"},"require_alias":{"type":"boolean","description":"If `true`, the destination must be an index alias.","x-found-in":"query"},"require_data_stream":{"type":"boolean","description":"If `true`, the request's actions must target a data stream (existing or to be created).","x-found-in":"query"},"document":{"x-found-in":"body"},"id":{"type":"string","description":"A unique identifier for the document.\nTo automatically generate a document ID, use the `POST /<target>/_doc/` request format and omit this parameter.","x-found-in":"path"},"index":{"type":"string","description":"The name of the data stream or index to target.\nIf the target doesn't exist and matches the name or wildcard (`*`) pattern of an index template with a `data_stream` definition, this request creates the data stream.\nIf the target doesn't exist and doesn't match a data stream template, this request creates the index.\nYou can check for existing targets with the resolve index API.","x-found-in":"path"}},"required":["index"],"description":"Create or update a document in an index.\n\nAdd a JSON document to the specified data stream or index and make it searchable.\nIf the target is an index and the document already exists, the request updates the document and increments its version.\n\nNOTE: You cannot use this API to send update requests for existing documents in a data stream.\n\nIf the Elasticsearch security features are enabled, you must have the following index privileges for the target data stream, index, or index alias:\n\n* To add or overwrite a document using the `PUT /<target>/_doc/<_id>` request format, you must have the `create`, `index`, or `write` index privilege.\n* To add a document using the `POST /<target>/_doc/` request format, you must have the `create_doc`, `create`, `index`, or `write` index privilege.\n* To automatically create a data stream or index with this API request, you must have the `auto_configure`, `create_index`, or `manage` index privilege.\n\nAutomatic data stream creation requires a matching index template with data stream enabled.\n\nNOTE: Replica shards might not all be started when an indexing operation returns successfully.\nBy default, only the primary is required. Set `wait_for_active_shards` to change this default behavior (this parameter is not available in Elasticsearch Serverless).\n\n**Automatically create data streams and indices**\n\nIf the request's target doesn't exist and matches an index template with a `data_stream` definition, the index operation automatically creates the data stream.\n\nIf the target doesn't exist and doesn't match a data stream template, the operation automatically creates the index and applies any matching index templates.\n\nNOTE: Elasticsearch includes several built-in index templates. To avoid naming collisions with these templates, refer to index pattern documentation.\n\nIf no mapping exists, the index operation creates a dynamic mapping.\nBy default, new fields and objects are automatically added to the mapping if needed.\n\nAutomatic index creation is controlled by the `action.auto_create_index` setting.\nIf it is `true`, any index can be created automatically.\nYou can modify this setting to explicitly allow or block automatic creation of indices that match specified patterns or set it to `false` to turn off automatic index creation entirely.\nSpecify a comma-separated list of patterns you want to allow or prefix each pattern with `+` or `-` to indicate whether it should be allowed or blocked.\nWhen a list is specified, the default behaviour is to disallow.\n\nNOTE: The `action.auto_create_index` setting affects the automatic creation of indices only.\nIt does not affect the creation of data streams.\n\n**Optimistic concurrency control**\n\nIndex operations can be made conditional and only be performed if the last modification to the document was assigned the sequence number and primary term specified by the `if_seq_no` and `if_primary_term` parameters.\nIf a mismatch is detected, the operation will result in a `VersionConflictException` and a status code of `409`.\n\n**Routing**\n\nBy default, shard placement — or routing — is controlled by using a hash of the document's ID value.\nFor more explicit control, the value fed into the hash function used by the router can be directly specified on a per-operation basis using the `routing` parameter.\n\nWhen setting up explicit mapping, you can also use the `_routing` field to direct the index operation to extract the routing value from the document itself.\nThis does come at the (very minimal) cost of an additional document parsing pass.\nIf the `_routing` mapping is defined and set to be required, the index operation will fail if no routing value is provided or extracted.\n\nNOTE: Data streams do not support custom routing unless they were created with the `allow_custom_routing` setting enabled in the template.\n\n**Distributed**\n\nThe index operation is directed to the primary shard based on its route and performed on the actual node containing this shard.\nAfter the primary shard completes the operation, if needed, the update is distributed to applicable replicas.\n\n**Active shards**\n\nTo improve the resiliency of writes to the system, indexing operations can be configured to wait for a certain number of active shard copies before proceeding with the operation.\nIf the requisite number of active shard copies are not available, then the write operation must wait and retry, until either the requisite shard copies have started or a timeout occurs.\nBy default, write operations only wait for the primary shards to be active before proceeding (that is to say `wait_for_active_shards` is `1`).\nThis default can be overridden in the index settings dynamically by setting `index.write.wait_for_active_shards`.\nTo alter this behavior per operation, use the `wait_for_active_shards request` parameter (this parameter is not available in Elasticsearch Serverless).\n\nValid values are all or any positive integer up to the total number of configured copies per shard in the index (which is `number_of_replicas`+1).\nSpecifying a negative value or a number greater than the number of shard copies will throw an error.\n\nFor example, suppose you have a cluster of three nodes, A, B, and C and you create an index index with the number of replicas set to 3 (resulting in 4 shard copies, one more copy than there are nodes).\nIf you attempt an indexing operation, by default the operation will only ensure the primary copy of each shard is available before proceeding.\nThis means that even if B and C went down and A hosted the primary shard copies, the indexing operation would still proceed with only one copy of the data.\nIf `wait_for_active_shards` is set on the request to `3` (and all three nodes are up), the indexing operation will require 3 active shard copies before proceeding.\nThis requirement should be met because there are 3 active nodes in the cluster, each one holding a copy of the shard.\nHowever, if you set `wait_for_active_shards` to `all` (or to `4`, which is the same in this situation), the indexing operation will not proceed as you do not have all 4 copies of each shard active in the index.\nThe operation will timeout unless a new node is brought up in the cluster to host the fourth copy of the shard.\n\nIt is important to note that this setting greatly reduces the chances of the write operation not writing to the requisite number of shard copies, but it does not completely eliminate the possibility, because this check occurs before the write operation starts.\nAfter the write operation is underway, it is still possible for replication to fail on any number of shard copies but still succeed on the primary.\nThe `_shards` section of the API response reveals the number of shard copies on which replication succeeded and failed.\n\n**No operation (noop) updates**\n\nWhen updating a document by using this API, a new version of the document is always created even if the document hasn't changed.\nIf this isn't acceptable use the `_update` API with `detect_noop` set to `true`.\nThe `detect_noop` option isn't available on this API because it doesn’t fetch the old source and isn't able to compare it against the new source.\n\nThere isn't a definitive rule for when noop updates aren't acceptable.\nIt's a combination of lots of factors like how frequently your data source sends updates that are actually noops and how many queries per second Elasticsearch runs on the shard receiving the updates.\n\n**Versioning**\n\nEach indexed document is given a version number.\nBy default, internal versioning is used that starts at 1 and increments with each update, deletes included.\nOptionally, the version number can be set to an external value (for example, if maintained in a database).\nTo enable this functionality, `version_type` should be set to `external`.\nThe value provided must be a numeric, long value greater than or equal to 0, and less than around `9.2e+18`.\n\nNOTE: Versioning is completely real time, and is not affected by the near real time aspects of search operations.\nIf no version is provided, the operation runs without any version checks.\n\nWhen using the external version type, the system checks to see if the version number passed to the index request is greater than the version of the currently stored document.\nIf true, the document will be indexed and the new version number used.\nIf the value provided is less than or equal to the stored document's version number, a version conflict will occur and the index operation will fail. For example:\n\n```\nPUT my-index-000001/_doc/1?version=2&version_type=external\n{\n  \"user\": {\n    \"id\": \"elkbee\"\n  }\n}\n```\n\nIn this example, the operation will succeed since the supplied version of 2 is higher than the current document version of 1.\nIf the document was already updated and its version was set to 2 or higher, the indexing command will fail and result in a conflict (409 HTTP status code).\n\nA nice side effect is that there is no need to maintain strict ordering of async indexing operations run as a result of changes to a source database, as long as version numbers from the source database are used.\nEven the simple case of updating the Elasticsearch index using data from a database is simplified if external versioning is used, as only the latest version will be used if the index operations arrive out of order."}