Tradeoffs _all and multiple terms

Hi all.

I've a use case where I need to use a free search, so I need to search on all fields. I know that have some important information about _all in the documentation:

"The _all field can be useful, especially when exploring new data using simple filtering. However, by concatenating field values into one big string, the _all field loses the distinction between short fields (more relevant) and long fields (less relevant). For use cases where search relevance is important, it is better to query individual fields specifically."

In my use case, I have control about all mappings (Dynamic mapping is not allowed) so I could search for all fields using multiple terms. So, I'm thinking about tradeoffs in doing a search for all terms (about 30 fields) or is better to use the _all. I need to use n-gram because I assume some typos on texts that will be indexed.

Does someone have some reference to get more details about it ou someone already used that approach? I'm searching for some opinion before start a Proof of Concept for that.
I want to discovery if the cost (CPU, memory, disk) of use _all analyzed as n-gram will be better or worse than searching on all fields.

Thanks a lot


I got my answer on that presentation


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.