Possibility to configure max_analyzed_offset in highlight request

[dcolazin]

Describe the feature: currently, if highlighting is enabled, Kibana performs an highlight request with only "pre_tags", "post_tags", "fields" and "fragment_size" attributes when querying Elastic. There are many other attributes that might be useful to configure for an highlight request. In my case, "max_analyzed_offset" would be very useful to bypass the shard failures when the searched field is longer than the index setting (default 1000000) without disabling highlighting in Kibana or changing the config on Elastic that might degrade performance (increase the default index setting, using offsets or term vectors).

Describe a specific use case for the feature: with a default of 1000000 (or 999999 if we are scared by off-by-one errors!), it will possible to completely avoid shard failures (if also Elastic config is set to default) in case of fields longer than 1MB. Even without setting a default, it will be possible to readily solve the issue on Kibana-side.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.

[dcolazin]

Quite sad to see Kibana not supporting a straightforward Elasticsearch feature as "not planned"...

[kertal]

@dcolazin it's currently not planned, we agree it makes sense, but we currently can't provide a realistic implementation path for it. Also for this feature we'd need to provide UI, or would this be a general configuration option for all highlight requests?

[iamgd67]

may close by #191384