I'm using Search API with a database backend and Views to build the search results page. More specifically, I'm using fields in Views. When selecting fields, I see two options for example:
When using this field, I get the same result. So I'm wondering why might I use the indexed version over the regular?
Simple:
For example: You have 1000 contents, and you want to show 10 of these, titles of that starts "Z" letter.
If you use Title as filter - Drupal will use it by Views handlers, so:
As you see - it's not good for performance. Better is using Title (indexed field)as Views filter, that will request only required 10 records from SOLR server.
p.s. Against it, title will prefer for Views output than indexed field (for some cases).
Titleprovided for Views from Entity.Title (indexed field)provided for Views from SOLR. For example: If you useTitleas filter - Drupal will use it by own filter handlers. So first, it will request data from SOLR (for example 100 found rows), then Views make filter on found rows, reducing it to 10 found rows - as you see - it's not good for performance. Better is usingTitle (indexed field), that will request only 10 records from SOLR server. Against,titlewill more preferred for outputs, than indexed fields (for some cases).Indexed fieldgrabs the field from the search API index, rather than the Drupal database. SoIndexed fieldprobably the one you want.