Thanks.
It is a fairly large ACL, so I am hoping to avoid any sort of application
redirect. That is sort of the problem we are trying to solve actually. Our
list was getting too large and we were maxing out maxBooleanQueries.
And I don't know which shard the user document is located on, just its
How much information do you need from this document? If it's a reasonably small
amount, can you read it at the application layer and attach it as a
set of parameters
to the query that are then available to the post filter. Or is it a
huge ACL list of something
In this latter case, if you know
I have created a PostFilter. PostFilter creates a DelegatingCollector,
which provides a Lucene IndexSearcher.
However, I need to query for an object that may or may not be located on
the shard that I am filtering on.
Normally, I would do something like:
searcher.search(new TermQuery(new Term("fi
