: I don't use Filters very much so this might be a dumb question, but I : could overcome the main drawback by hooking into the filter and : updating it's bits without affecting the caching, right?
Not really ... Solr doesn't use Filter's the same way as CachingWrapperFilter does ... it builds DocSet's out of them and cachines those for the life of the IndexSearcher (or until the cache gets full and it needs to expunge somehting) when a new IndexSearcher is opened, it auto-warms the new filterCache by executing hte exsiting Filter's against the new IndexSearcher. : I kind of think I have scaling issues no matter what. If you do the : post processing way, then you may have to make repeated fetches to : Solr in order to get enough results to display. anything you can do on the client side you can do in a custom request handler (assuming you cna do it in java) so that will at least save you the overhead of HTTP back and forth with the Solr server ... i was jsut trying to think of ways that existing features available to SolrRequestHandlers could help you more. -Hoss
