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 filter is called for any documents on the second shard.
On Fri, Mar 20, 2015 at 4:12 PM, Kevin Osborn <kosb...@centraldesktop.com>
wrote:
> 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 then tried this filter in a two-shard environment. This time things
> did not work well. I am still trying to figure out what is going on, but it
> seems like just the first shard is being used. I get the same results no
> matter what shard or replica I begin my query on. But it seems like the
> results are not being merged.
>
> Although I am still trying to figure out if the second shard is even being
> queried.
>
> Are there any known issues with DelegatingCollector and shards?
>
> I don't know if this is related, but I did once get the following error
> message as well.
>
> java.lang.UnsupportedOperationException: Query {!cache=false cost=100} does
> not implement
> createWeight
>
>
