Whew! Thanks for bring this to closure!
Best,
Erick
On Mon, Mar 23, 2015 at 9:18 AM, Kevin Osborn
wrote:
> I think I found my issue. It has nothing to do with the post filter. In the
> constructor of my post filter, I am doing a TermQuery do get a single user
> document. I then later intersect t
I think I found my issue. It has nothing to do with the post filter. In the
constructor of my post filter, I am doing a TermQuery do get a single user
document. I then later intersect this user's permissions with the collected
documents. So, if the user document is in the shard that I am filtering
A little more information here. I have verified that the post filter is
giving me only documents that are in the first shard. Running two shards
and a single replica in debug mode also shows that the collect method is
only called for documents in the first shard. I never see any indication
that the
I developed a post filter. My documents to be filtered are on two different
shards. So, in a single-shard environment,
DelegatingCollector.doSetNextReader is called twice. And collect is called
the correct number of times. Everything went well and I got my correct
number of results back.
So, I the
