mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-14 08:55:19 +00:00
36a3b84fc9
* Default include_type_name to false for get and put mappings. * Default include_type_name to false for get field mappings. * Add a constant for the default include_type_name value. * Default include_type_name to false for get and put index templates. * Default include_type_name to false for create index. * Update create index calls in REST documentation to use include_type_name=true. * Some minor clean-ups around the get index API. * In REST tests, use include_type_name=true by default for index creation. * Make sure to use 'expression == false'. * Clarify the different IndexTemplateMetaData toXContent methods. * Fix FullClusterRestartIT#testSnapshotRestore. * Fix the ml_anomalies_default_mappings test. * Fix GetFieldMappingsResponseTests and GetIndexTemplateResponseTests. We make sure to specify include_type_name=true during xContent parsing, so we continue to test the legacy typed responses. XContent generation for the typeless responses is currently only covered by REST tests, but we will be adding unit test coverage for these as we implement each typeless API in the Java HLRC. This commit also refactors GetMappingsResponse to follow the same appraoch as the other mappings-related responses, where we read include_type_name out of the xContent params, instead of creating a second toXContent method. This gives better consistency in the response parsing code. * Fix more REST tests. * Improve some wording in the create index documentation. * Add a note about types removal in the create index docs. * Fix SmokeTestMonitoringWithSecurityIT#testHTTPExporterWithSSL. * Make sure to mention include_type_name in the REST docs for affected APIs. * Make sure to use 'expression == false' in FullClusterRestartIT. * Mention include_type_name in the REST templates docs.
73 lines
2.2 KiB
Plaintext
73 lines
2.2 KiB
Plaintext
[[query-dsl-nested-query]]
|
|
=== Nested Query
|
|
|
|
Nested query allows to query nested objects / docs (see
|
|
<<nested,nested mapping>>). The
|
|
query is executed against the nested objects / docs as if they were
|
|
indexed as separate docs (they are, internally) and resulting in the
|
|
root parent doc (or parent nested mapping). Here is a sample mapping we
|
|
will work with:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
PUT /my_index?include_type_name=true
|
|
{
|
|
"mappings": {
|
|
"_doc" : {
|
|
"properties" : {
|
|
"obj1" : {
|
|
"type" : "nested"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
// TESTSETUP
|
|
|
|
And here is a sample nested query usage:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
GET /_search
|
|
{
|
|
"query": {
|
|
"nested" : {
|
|
"path" : "obj1",
|
|
"score_mode" : "avg",
|
|
"query" : {
|
|
"bool" : {
|
|
"must" : [
|
|
{ "match" : {"obj1.name" : "blue"} },
|
|
{ "range" : {"obj1.count" : {"gt" : 5}} }
|
|
]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
|
|
The query `path` points to the nested object path, and the `query`
|
|
includes the query that will run on the nested docs matching the
|
|
direct path, and joining with the root parent docs. Note that any
|
|
fields referenced inside the query must use the complete path (fully
|
|
qualified).
|
|
|
|
The `score_mode` allows to set how inner children matching affects
|
|
scoring of parent. It defaults to `avg`, but can be `sum`, `min`,
|
|
`max` and `none`.
|
|
|
|
There is also an `ignore_unmapped` option which, when set to `true` will
|
|
ignore an unmapped `path` and will not match any documents for this query.
|
|
This can be useful when querying multiple indexes which might have different
|
|
mappings. When set to `false` (the default value) the query will throw an
|
|
exception if the `path` is not mapped.
|
|
|
|
Multi level nesting is automatically supported, and detected, resulting
|
|
in an inner nested query to automatically match the relevant nesting
|
|
level (and not root) if it exists within another nested query.
|