[DOCS] Updated memory considerations for p/c queries and filters.

docs/reference/query-dsl/filters/has-child-filter.asciidoc

@@ -45,9 +45,9 @@ The `has_child` filter also accepts a filter instead of a query:
 [float]
 ==== Memory Considerations
 
-With the current implementation, all `_id` values are loaded to memory
-(heap) in order to support fast lookups, so make sure there is enough
-memory for it.
+With the current implementation, all `_parent` field values and all `_id`
+field values of parent documents are loaded into memory (heap) via field data
+in order to support fast lookups, so make sure there is enough memory for it.
 
 [float]
 ==== Caching

docs/reference/query-dsl/filters/has-parent-filter.asciidoc

@@ -48,9 +48,9 @@ The `has_parent` filter also accepts a filter instead of a query:
 [float]
 ==== Memory considerations
 
-With the current implementation, all `_id` values are loaded to memory
-(heap) in order to support fast lookups, so make sure there is enough
-memory for it.
+With the current implementation, all `_parent` field values and all `_id`
+field values of parent documents are loaded into memory (heap) via field data
+in order to support fast lookups, so make sure there is enough memory for it.
 
 [float]
 ==== Caching

docs/reference/query-dsl/queries/has-child-query.asciidoc

@@ -56,6 +56,6 @@ inside the `has_child` query:
 [float]
 ==== Memory Considerations
 
-With the current implementation, all `_id` values are loaded to memory
-(heap) in order to support fast lookups, so make sure there is enough
-memory for it.
+With the current implementation, all `_parent` field values and all `_id`
+field values of parent documents are loaded into memory (heap) via field data
+in order to support fast lookups, so make sure there is enough memory for it.

docs/reference/query-dsl/queries/has-parent-query.asciidoc

@@ -52,6 +52,6 @@ matching parent document. The score type can be specified with the
 [float]
 ==== Memory Considerations
 
-With the current implementation, all `_id` values are loaded to memory
-(heap) in order to support fast lookups, so make sure there is enough
-memory for it.
+With the current implementation, all `_parent` field values and all `_id`
+field values of parent documents are loaded into memory (heap) via field data
+in order to support fast lookups, so make sure there is enough memory for it.

docs/reference/query-dsl/queries/top-children-query.asciidoc

@@ -66,6 +66,6 @@ same scope name that will work against the child documents. For example:
 [float]
 ==== Memory Considerations
 
-With the current implementation, all `_id` values are loaded to memory
-(heap) in order to support fast lookups, so make sure there is enough
-memory for it.
+With the current implementation, all `_parent` field values and all `_id`
+field values of parent documents are loaded into memory (heap) via field data
+in order to support fast lookups, so make sure there is enough memory for it.