-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docvalue_fields support wildcard? #26299
Comments
Agreed we should support it for consistency. |
We discussed it in FixitFriday. We agreed to do this, but at the same time we should probably add a soft limit over the number of doc_values and script fields that are requested (computed based on the number of matches in the mappings) since doc-values fields come up with a per-field per-document seek (while stored fields only incur a per-document seek regardless of the number of fields). |
I opened #26390. |
/cc @elastic/es-search-aggs |
any updates here? I have object with 60 fields and all of them are needed to be extracted |
@serdyuk-alex the issue is still marked as "adoptme", it is not implemented yet. |
I don't think this is feasible without changing how docvalue_fields work. For example the following query:
throws an exception:
Therefore if "*" is expand to all fields (which I believe it should include metadata fields), it will always result on an error. Note that for stored_fields, fields are ignored if they are not stored. |
Requesting doc-value fields on all fields is likely going to fail all the time anyway because of the soft limit that we plan to introduce, it will only be possible to use wildcards that match a very narrow set of fields. I think we should implement support for wildcards regardless of the fact that some fields don't support it? |
For consistency with stored_fields, docvalue_fields should support the use of wildcards. See also: elastic#26390 Closes elastic#26299
Hi, all.
When using docvalue_fields, we would like to use wildcard like stored_fields:
Looking forward to this feature.
The text was updated successfully, but these errors were encountered: