We are working on integration with the Drupal CMS, and so are writing code that carries out operations that might only be relevant for only a small subset of the sites/indexes that might use the integration module. In this regard, I'm wondering if adding to the query (using the dismax or mlt handlers) a fq that matches all documents would have any impact on performance? I gatehr that there is caching for the fq matches, but it seems liek that would still incur some overhead, especially for a large index?
As a more concrete example, suppose each document has a string field that names the role of user that is allowed to see the content. e.g. 'public', 'registered', 'admin'. Most sites have only public content, but because our code is generic, we might add &fq=role:public to every query. What would the expected performance effect be compared to omitting that fq if, for example, we had a way to determine in advance that all site content matches 'public'. Thanks, Peter -- Peter M. Wolanin, Ph.D. Momentum Specialist, Acquia. Inc. peter.wola...@acquia.com
