What on earth is FilteredQuery.explain doing?

Hi all. In this test, I wrap a query in a FilteredQuery. Then I do a query which returns one doc and pass that doc ID to get an explanation. The resulting Explanation.isMatch() returns false, which seems odd, considering it was obviously a match. Is this a bug? Code follows. TX public class T

Dynamic faceting with multi value numeric fields

Hi, I am implementing dynamic faceting as described here - http://www.norconex.com/facets-with-lucene/ and running into trouble for multi value facets. For strings this is not a problem. One can use SortedSetDocValuesFacetField when indexing the values for faceting and SortedSetDocValuesFacetCo

Re: What on earth is FilteredQuery.explain doing?

TX, This looks like a bug that has already been fixed on branch_5x as part of LUCENE-6601 . The bug is in org.apache.search.Filter.createWeight: public Explanation explain(LeafReaderContext context, int doc) throws IOException { fi

Re: What on earth is FilteredQuery.explain doing?

On Wed, Jul 15, 2015 at 4:50 AM, Terry Smith wrote: > > This looks like a bug that has already been fixed on branch_5x as part of > LUCENE-6601 . The bug is > in org.apache.search.Filter.createWeight: [snip] > Here you can see it calls Explanation

Re: What on earth is FilteredQuery.explain doing?

The Explanation is "interesting"... 1 = {org.apache.lucene.search.Explanation@1836} "0.0 = No match on id 0\n" match = true value = 0.0 description = {java.lang.String@1839} "No match on id 0" details = {java.util.Collections$UnmodifiableRandomAccessList@1840}