It seems that ConstantScoreQuery use the Weight and Score of the Query it
wrapperd, like TermWeight and TermScorer , so it can't speed up the search,
because the weight and score is still calculated. Maybe i make it wrong, but i
did some test, the search time of ‘ new ConstantScoreQuery(new T
ConstantScoreQuery is the proper approach. What specific failure did you
encounter?
-- Jack Krupansky
On Wed, Jul 29, 2015 at 7:09 AM, 丁儒 wrote:
> Hi, all
> Currently i'm using lucene. But i don't care the score and weight, i
> just need the documents meets the query. I tried some way to ig
Hi, all
Currently i'm using lucene. But i don't care the score and weight, i just
need the documents meets the query. I tried some way to ignore the score, like
rewrite TermQury, disable the TermWeight and TermScore, but there are a lot of
queries, and this is incompatible with QueryParser.
Thanks Anton for your suggestion, also if we specify 2 criteria in search
query, can we identify which criteria causes the match ?
On Tue, Jul 28, 2015 at 9:04 PM, Anton Zenkov
wrote:
> You can always throw an exception in the collector to stop the collection
> process.
>
> Anton
>
> On Tue, Jul