We need to aggregate Strawberry Flavors at the ADO level for unified search to happen (performance reasons means a subquery is a bad idea given how Drupal Views work related to Search API functionality...)
The idea is basic. An ADO Solr Document is ready way before all their Flavor Children are ready. So we need a performant way (means not on every Child generation) to tell Solr that the parent needs to be reindexed so it can gather all the little children at once.
This also means we need a Computed (global field?) That does the gathering:
Two options:
Use the same idea of the one that already exist and renders a View Mode, but this one will do "a Solr query" to gather all Text only Values from all Flavors.
Add logic to the Key Name provider we already have for this and do the logic there. Means expose the Text as a Field property.
DiegoPino
commented
1 year ago
What?
We need to aggregate Strawberry Flavors at the ADO level for unified search to happen (performance reasons means a subquery is a bad idea given how Drupal Views work related to Search API functionality...)
The idea is basic. An ADO Solr Document is ready way before all their Flavor Children are ready. So we need a performant way (means not on every Child generation) to tell Solr that the parent needs to be reindexed so it can gather all the little children at once.
This also means we need a Computed (global field?) That does the gathering: Two options: