: We had exactly this problem in a consumer app; we had a small but : continuously growing list of obscene documents in the index, and did : not want to display these. So, we had a filter query with all of the : obscene words, and used this with every query.
that doesn't seem like it would really help with the caching issue ... the reusing the FieldCache seems like hte only thing that would be advantageous in that case, the filterCache and queryResultCache are going to have a low cache hit rate as the filter queries involved keep changing as new doc eys get added to the filter query. or am i completely missunderstanding how you had this working? -Hoss
