honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/reference/query-dsl/parent-id-query.asciidoc

72 lines
1.5 KiB
Plaintext
Raw Normal View History

Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
[[query-dsl-parent-id-query]]
[DOCS] Make Query DSL titles consistent (#43935)
2019-07-18 10:18:11 -04:00
=== Parent ID query
++++
<titleabbrev>Parent ID</titleabbrev>
++++
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
Merge branch 'master' into docs/add_autosense_to_query_dsl
2016-05-17 15:12:06 -04:00
The `parent_id` query can be used to find child documents which belong to a particular parent.
Given the following mapping definition:
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
Docs: Clarified the purpose of the parent_id query
2016-04-14 05:25:26 -04:00
[source,js]
Merge branch 'master' into docs/add_autosense_to_query_dsl
2016-05-17 15:12:06 -04:00
--------------------------------------------
Remove remaining occurances of "include_type_name=true" in docs (#37646)
2019-01-22 09:13:52 -05:00
PUT my_index
Docs: Clarified the purpose of the parent_id query
2016-04-14 05:25:26 -04:00
{
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
"mappings": {
Remove remaining occurances of "include_type_name=true" in docs (#37646)
2019-01-22 09:13:52 -05:00
"properties": {
"my_join_field": {
"type": "join",
"relations": {
"my_parent": "my_child"
Fix test failures.
2016-05-12 06:29:18 -04:00
}
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
}
Adds ignore_unmapped option to nested and P/C queries The change adds a new option to the `nested`, `has_parent`, `has_children` and `parent_id` queries: `ignore_unmapped`. If this option is set to false, the `toQuery` method on the QueryBuilder will throw an exception if the type/path specified in the query is unmapped. If the option is set to true, the `toQuery` method on the QueryBuilder will return a MatchNoDocsQuery. The default value is `false`so the queries work how they do today (throwing an exception on unmapped paths/types)
2016-04-14 04:37:18 -04:00
}
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
}
Docs: Clarified the purpose of the parent_id query
2016-04-14 05:25:26 -04:00
}
Add a wait_for_stats=yellow to a docs snippet It was making unstable tests.
2016-05-18 15:10:01 -04:00
Allow `_doc` as a type. (#27816) Allowing `_doc` as a type will enable users to make the transition to 7.0 smoother since the index APIs will be `PUT index/_doc/id` and `POST index/_doc`. This also moves most of the documentation to `_doc` as a type name. Closes #27750 Closes #27751
2017-12-14 11:47:53 -05:00
PUT my_index/_doc/1?refresh
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
{
"text": "This is a parent document",
"my_join_field": "my_parent"
}
Docs: Clarified the purpose of the parent_id query
2016-04-14 05:25:26 -04:00
Allow `_doc` as a type. (#27816) Allowing `_doc` as a type will enable users to make the transition to 7.0 smoother since the index APIs will be `PUT index/_doc/id` and `POST index/_doc`. This also moves most of the documentation to `_doc` as a type name. Closes #27750 Closes #27751
2017-12-14 11:47:53 -05:00
PUT my_index/_doc/2?routing=1&refresh
Fix test failures.
2016-05-12 06:29:18 -04:00
{
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
"text": "This is a child document",
"my_join_field": {
"name": "my_child",
"parent": "1"
}
Fix test failures.
2016-05-12 06:29:18 -04:00
}
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
--------------------------------------------
// CONSOLE
// TESTSETUP
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
[source,js]
--------------------------------------------------
Add back doc execution to query dsl. Relates to #18211 This reverts commit 20aafb1196192d4f9f7faea8ce9a36b278e501a1.
2016-05-24 05:58:43 -04:00
GET /my_index/_search
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
{
Add back doc execution to query dsl. Relates to #18211 This reverts commit 20aafb1196192d4f9f7faea8ce9a36b278e501a1.
2016-05-24 05:58:43 -04:00
"query": {
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
"parent_id": {
"type": "my_child",
"id": "1"
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
}
Revert "Add Autosense annotation for query dsl testing"
2016-05-17 14:55:56 -04:00
}
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
}
--------------------------------------------------
Add back doc execution to query dsl. Relates to #18211 This reverts commit 20aafb1196192d4f9f7faea8ce9a36b278e501a1.
2016-05-24 05:58:43 -04:00
// CONSOLE
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
Cleanup ParentFieldMapper: * Remove remaining 1.x bwc logic. * Stop storing stored fields and indexed terms. The _parent field's only purpose is to support joins between parent and child type and only storing doc values is sufficient. * In the mapping the parent field mapper is now known under '{parent}#{child}' key, because this is the field the parent/child join uses too. * Added new sub fetch phase to lookup that _parent field from doc values field if that is required (before this was fetched from stored _parent field) * Removed the ability to query directly on `_parent` in the query dsl. Instead the `{parent}#{child}` field should be used. Under the hood a doc values query is used instead of a term query, because only doc values fields are stored now. * Added a new `parent_id` query to easily query child documents with a specific parent id without having to know what join field to use * Also in aggregations `_parent` field can't be used any more and `{parent}#{child}` field name should be used instead to aggregate directly on the _parent join field.
2016-01-17 16:49:07 -05:00
==== Parameters
This query has two required parameters:
[horizontal]
Remove usage of multi-types from the docs and added a page explaining type removal (#25543) Closes #25401
2017-07-05 06:30:19 -04:00
`type`:: The **child** type name, as specified in the <<parent-join,`join` field>>.
`id`:: The ID of the parent document.
Adds ignore_unmapped option to nested and P/C queries The change adds a new option to the `nested`, `has_parent`, `has_children` and `parent_id` queries: `ignore_unmapped`. If this option is set to false, the `toQuery` method on the QueryBuilder will throw an exception if the type/path specified in the query is unmapped. If the option is set to true, the `toQuery` method on the QueryBuilder will return a MatchNoDocsQuery. The default value is `false`so the queries work how they do today (throwing an exception on unmapped paths/types)
2016-04-14 04:37:18 -04:00
Add a wait_for_stats=yellow to a docs snippet It was making unstable tests.
2016-05-18 15:10:01 -04:00
`ignore_unmapped`:: When set to `true` this will ignore an unmapped `type` and will not match any
Adds ignore_unmapped option to nested and P/C queries The change adds a new option to the `nested`, `has_parent`, `has_children` and `parent_id` queries: `ignore_unmapped`. If this option is set to false, the `toQuery` method on the QueryBuilder will throw an exception if the type/path specified in the query is unmapped. If the option is set to true, the `toQuery` method on the QueryBuilder will return a MatchNoDocsQuery. The default value is `false`so the queries work how they do today (throwing an exception on unmapped paths/types)
2016-04-14 04:37:18 -04:00
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 `type` is not mapped.