If you create an mapping containing an ignore_above field and ingest values that are above that limit, those are not returned by via the fields API. Since we're using the fields API nowadays in Discover this is a rather severe regression we found. From my experience we often have people having fields containing values above those limits, which were with reading from _source available and visible to the users. Using the new fields API, those will simply return as empty and no longer show in Discover.
It would be good if we can include those values in the response (whether behind a request flag, similar to include_unmapped or by default).
Related Kibana issue: elastic/kibana#101232
If you create an mapping containing an
ignore_abovefield and ingest values that are above that limit, those are not returned by via the fields API. Since we're using the fields API nowadays in Discover this is a rather severe regression we found. From my experience we often have people having fields containing values above those limits, which were with reading from_sourceavailable and visible to the users. Using the new fields API, those will simply return as empty and no longer show in Discover.It would be good if we can include those values in the response (whether behind a request flag, similar to
include_unmappedor by default).Related Kibana issue: elastic/kibana#101232