Timeline for What's the difference between indexed and non-indexed field in Views and Search API?
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 8, 2021 at 3:00 | history | tweeted | twitter.com/StackDrupal/status/1390864110615662604 | ||
May 7, 2021 at 15:07 | vote | accept | chrisck | ||
May 6, 2021 at 1:20 | comment | added | Nikit | @kiamlaluno ok, I have copy to answers. | |
May 6, 2021 at 1:20 | answer | added | Nikit | timeline score: 1 | |
Apr 29, 2021 at 21:02 | comment | added | avpaderno♦ | @Nikit That seems an answer. | |
Apr 28, 2021 at 7:57 | comment | added | chrisck | Thanks for both of your answers. Makes perfect sense. | |
Apr 28, 2021 at 6:14 | comment | added | 100pic |
TLDR: Indexed field grabs the field from the search API index, rather than the Drupal database. So Indexed field probably the one you want.
|
|
Apr 28, 2021 at 1:04 | comment | added | Nikit |
Simple: Title provided for Views from Entity. Title (indexed field) provided for Views from SOLR. For example: If you use Title as 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 using Title (indexed field) , that will request only 10 records from SOLR server. Against, title will more preferred for outputs, than indexed fields (for some cases).
|
|
Apr 27, 2021 at 20:15 | history | asked | chrisck | CC BY-SA 4.0 |