: In Solr 3.x, I was relying on a postCommit call to a listener in the update : handler to perform data update to caches, this data was used to perform : 'realtime' filtering on the documents.
I can't find it at the moment, but IIRC this was a side effect of how snapshots are now loaded on slaves -- there is no longer an explicit "commit" to read in the new index. For your usecase however, i think what would make more sense (and probably would have always made more sense) is to implement this using the "newSearcher" hook, which allows you to block usage of the newSearcher until you have finished your hook logic. Alternatively, you can implement CacheRegenerator which was specifically designed for warming caches on newSearcher events, and gives you access to the current cache keys so you can see what items where in the old caches to warm. -Hoss
