Search over large documents

Elastic Stack Elasticsearch
1

hi all

we have an index in ES which we use both for search and display on UI for resource card. this card is shown for user when he clicks on a title from search results, and document is get there by it's id. so, about 10% fields are indexed, other 90% are just stored in index as source with "index: false".

does it make sense to split this data into 2 separate indexes - so, first one will contain only fields we need for search/filter/aggregate and display on search results page, and other will contain all remaining fields? will it improve search performance? or it doesn't matter a lot how big is document, because anyway ES uses inverted index for indexed fields and just read source documents then for found ones? will benefit of such splitting be significant here?

thanks in advance for answer

2

It'll make a difference when it needs to do the fetch phase of a search. The overview here is for an older Elasticsearch version, but it's still valid.

3

so, on search phase performance will be quite the same for both cases, right?

4

I suspect keeping the data in a single index/document will be faster as there will be fewer queries and disk seeks to retrieve all the data.

5

sorry for not clear explanation, for search i need only data stored in first index, i will search over it and display on search results page. then only when user clicks on some result, i will send request to second index by document id to retrieve a document will all remaining fields to display.
will it be faster than store all fields initially in on document?

6

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