Currently when an aggregated field is added or changed the persistent cache is not cleared. The user has to manually do a cache clear before the aggregated field appears in the fields tab.
Expected result: the new aggregated field appears in the list.
Actual result: the field does not appear, only after manually clearing the caches the field becomes visible.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2305755-4--clear_cache_when_index_is_saved.patch | 2.07 KB | drunken monkey |
| #3 | 2305755-3--clear_cache_when_index_is_saved.patch | 2.07 KB | drunken monkey |
| #1 | 2305755-1-search_api-aggregated_field_cache.patch | 1.02 KB | pfrenssen |
Comments
Comment #1
pfrenssenPatch uses
drupal_array_diff_assoc_recursive()which was added in Drupal 7.23 so this raises the required minimum Drupal version.If this is a problem we can backport it as a protected method, or rename it as search_api_array_diff_assoc_recursive().
Comment #2
pfrenssenComment #3
drunken monkeyThanks for reporting!
You're right, for some reason we clear the static cache when saving the index, but not the persistent one, instead trying to only do that when it's really necessary. We could add additional code that makes sure the available fields also stay the same, but I think it makes more sense to just get rid of that and always clear the persistent cache, too, when editing the index. It shouldn't happen that often, after all.
Patch attached.
Comment #4
drunken monkeyOops, the previous patch would have failed to call
fieldsUpdated()when the fields change. Good thing I just spotted this when I wanted to commit …Could you please test the attached patch and see if that works for you? Then I would commit it in a few days.
Comment #5
drunken monkeyCommitted.