Kibana Feature : ability to disable highlight for a field or atleast index

[divit00]

Describe the feature:

In Kibana, we often face the issue with index.max.analyzed_offset greater than 1000000.

To solve this we can either increase its value to greater than 1000000 but it will make the query slower.

Or, we can use term_vectors but that would increase the size.

Or, we can disable doc_table:highlight in Kibana advanced settings to disable highlight completely for all indices. That is also not perfect because highlights are useful.

So, can we have a feature either to turn off highlights for

1. For a Index completely
2. For a Field in an Index. This would be best.

Either of the solution would work for me.

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[jbaggs]

So, can we have a feature either to turn off highlights for

1. For a Index completely

2. For a Field in an Index. This would be best.

Either of the solution would work for me.

With a project I am working on, I am running into this same issue. I would have the exact same preference of turning highlights off in a field over an index. The fields I would turn highlighting off for directly correlate with ones I turn off indexing for in Elasticsearch. (larger stuff I want to retrieve, but have already acknowledged is a bit beyond processing within ELK.)

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

[divit00]

I still believe this is an important issue to be fixed. Many people do come across this issue but they just turn off Kibana Highlights which isn't a good solution.

[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.

[JediExterm]

You guys really don't want to do this, huh? This enhancement would be a great benefit to my organization as well, especially since there seems to be no acceptable work around, requiring us to sacrifice speed, size, or highlighting in its entirety

[kertal]

@JediExterm It's not that we don't wanna do this. We see this would make sense, but we think it's better to communicate that it's not planned to be resolved in the foreseeable future. That's why it's "iceboxed". But we already implemented issues that were iceboxes before, because of change of priorities, or having new insights