this has some problems. First, your facet, group, num hits, etc. counts will be off for that user. Second, you can't sort without having all of the documents, so unless you're willing to have your counts be off, you really have to pay the price of post-filtering everything.
If you can live with the counts being off, consider just having the application do a couple of round-trips. Get the docs (oversample, say just get the IDs for the top 100 docs) _without_ any kind of ACL filtering. Then send those docs back to the server with the ACL filtering. If you don't get enough to fill up a response, get the next page of 100, etc..... Finally, the user's list is a better place for this kind of question, this list is for discussing developing the code... Best Erick On Wed, Jan 23, 2013 at 9:05 AM, Steve Molloy <smol...@opentext.com> wrote: > Hi, > > I'm looking for a way to apply filtering that unfortunately implies high > cost because it needs to access external resources (for security). I looked > at (and tried) the PostFilter technique, which offers some advantages, but > still imply a lot of matches in a lot of cases. What I'd like to be able to > do is to filter out ids until I have enough to fill the response, then stop > filtering (and accept everything). The idea being that total count is not as > important, major thing being results should not contain documents requester > should not see. So, post filter almost does the trick, except it comes > before sorting, so first X documents are not the same that the post filter > is getting. > > Is there a way to filter out documents after they have been scored and > sorted? > > Thanks, > Steve > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
