All methods and paths for this operation:
Validates a query without running it.
Path parameters
-
Comma-separated list of data streams, indices, and aliases to search. Supports wildcards (
*). To search all data streams or indices, omit this parameter or use*or_all.
Query parameters
-
A setting that does two separate checks on the index expression. If
false, the request returns an error (1) if any wildcard expression (including_alland*) resolves to zero matching indices or (2) if the complete set of resolved indices, aliases or data streams is empty after all expressions are evaluated. Iftrue, index expressions that resolve to no indices are allowed and the request returns an empty result.Default value is
true. -
If
true, the validation is executed on all shards instead of one random shard per index.Default value is
false. -
Analyzer to use for the query string. This parameter can only be used when the
qquery string parameter is specified. -
If
true, wildcard and prefix queries are analyzed.Default value is
false. -
The default operator for query string query:
andoror.Default value is
or. -
Field to use as default where no field prefix is given in the query string. This parameter can only be used when the
qquery string parameter is specified. -
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.Supported values include:
all: Match any data stream or index, including hidden ones.open: Match open, non-hidden indices. Also matches any non-hidden data stream.closed: Match closed, non-hidden indices. Also matches any non-hidden data stream. Data streams cannot be closed.hidden: Match hidden data streams and hidden indices. Must be combined withopen,closed, orboth.none: Wildcard expressions are not accepted.
Default value is
open. -
If
true, the response returns detailed information if an error has occurred.Default value is
false. -
If
true, format-based query failures (such as providing text to a numeric field) in the query string will be ignored.Default value is
false. -
If
true, returns a more detailed explanation showing the actual Lucene query that will be executed.Default value is
false. -
Query in the Lucene query string syntax.
-
A custom value used to route operations to a specific shard. Not allowed when
index.slice.enabledistruefor the target index; use_sliceinstead.
Body
-
Query in the Lucene query string syntax.
External documentation
GET my-index-000001/_validate/query?q=user.id:kimchy
resp = client.indices.validate_query(
index="my-index-000001",
q="user.id:kimchy",
)
const response = await client.indices.validateQuery({
index: "my-index-000001",
q: "user.id:kimchy",
});
response = client.indices.validate_query(
index: "my-index-000001",
q: "user.id:kimchy"
)
$resp = $client->indices()->validateQuery([
"index" => "my-index-000001",
"q" => "user.id:kimchy",
]);
curl -X GET -H "Authorization: ApiKey $ELASTIC_API_KEY" "$ELASTICSEARCH_URL/my-index-000001/_validate/query?q=user.id:kimchy"
var response = await client.Indices
.ValidateQueryAsync(d1 => d1
.Indices(new[] { "my-index-000001" })
.QueryLuceneSyntax("user.id:kimchy")
);
client.indices().validateQuery(v -> v
.index("my-index-000001")
.q("user.id:kimchy")
);