Hi all.

Filter is now deprecated, which I already knew was in the pipeline.

The docs say:

   "Use Query objects instead: when queries are wrapped in a
    ConstantScoreQuery or in a BooleanClause.Occur.FILTER clause,
    they automatically disable the score computation so the Filter
    class does not provide benefits compared to queries anymore."

That's fair enough and an easy change to do on the caller side.

The other thing we are using Filter for is the other thing it mentions
in the Javadoc:

   "Convenient base class for building queries that only perform
    matching, but no scoring. The scorer produced by such queries
    always returns 0 as score."

What is the new convenient way to implement your own queries that
don't do scoring?

TX

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Reply via email to