lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4378) QueryParsers do not support negative boosts
Date Wed, 12 Sep 2012 01:09:07 GMT


Hoss Man commented on LUCENE-4378:

bq. Dismissing my opinion isn't productive.

I don't see any one dismissing your opinion, i see yonik asking you to explain what you mean
by trappy since you seem to object to a feature on principle, when i've already listed an
example of a specific usecase where the people have asked for this to feature and functionally
it does work at the Query/Searcher/Explaination level -- it's only at the QueryParser level
that you can't use it.

bq. Right my problem with that is I think often people that want this don't really understand
the scoring system?

there are lots of things about the query parser that may not make sense to you if you don't
understand the scoring system -- that doesn't mean we don't support them, it's up to the user
to understand them if they want to use them.

As i said: i'm perfectly fine with the idea that something like this should not be supported
by default, and you should have to go out of your way to enable it in the QueryParser -- but
making people edit the grammer seems like forcing them to go too far out of their way.
> QueryParsers do not support negative boosts
> -------------------------------------------
>                 Key: LUCENE-4378
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Hoss Man
>         Attachments: LUCENE-4378-test.patch
> Negative query boosts have been supported at the "Query" object level for a long time
(resulting in negative scores for matching documents), but evidently we never updated the
QueryParsers to know about this - attempting to specify a negative boost in the query string
results in a parse error.
> we should probably add this to the parser grammer(s)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message