lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: How can I check if a more complex query condition matched?
Date Wed, 28 Dec 2011 13:52:54 GMT
There's no easy/efficient way that I know of to do this. Perhaps a good
question is what value-add this is going to make for your app and is
there a better way to convey this information. For instance, would
highlighting convey "enough" information to your user?

You're right that you don't want to enable debug in production, it
can take quite a long time (see the timings when you DO enable

Could you consider some kind of one-off when a user really, really
needs this info where you *do* add debugQuery=on but restrict
the query to a single document they're interested in?


On Wed, Dec 28, 2011 at 5:30 AM, Max <> wrote:
> Thanks for your reply, I thought about using the debug mode, too, but
> the information is not easy to parse and doesnt contain everything I
> want. Furthermore I dont want to enable debug mode in production.
> Is there anything else I could try?
> On Tue, Dec 27, 2011 at 12:48 PM, Ahmet Arslan <> wrote:
>>> I have a more complex query condition
>>> like this:
>>> (city:15 AND country:60)^4 OR city:15^2 OR country:60^2
>>> What I want to achive with this query is basically if a
>>> document has
>>> city = 15 AND country = 60 it is more important then
>>> another document
>>> which only has city = 15 OR country = 60
>>> Furhtermore I want to show in my results view why a certain
>>> document
>>> matched, something like "matched city and country" or
>>> "matched city
>>> only" or "matched country only".
>>> This is a bit of an simplified example, but the question
>>> remains: how
>>> can solr tell me which of the conditions in the query
>>> matched? If I
>>> match against a simple field only, I can get away with
>>> highlight
>>> fields, but conditions spanning multiple fields seem much
>>> more tricky.
>> Looks like you can extract these info from output of &debugQuery=on.

View raw message