lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <>
Subject [jira] [Commented] (SOLR-6039) debug=track causes debug=query info to be suprsedd when no results found
Date Fri, 02 May 2014 22:12:15 GMT


Tomás Fernández Löbbe commented on SOLR-6039:

bq.  i think for now it makes sense to just "fix" the bug relating ot wether the info comes
I agree now. When I started to think how to use max vs sum in some situations I saw the changes
were not trivial, better to leave that for a different Jira. 

I was about to upload a new patch with some more changes and tests, please give me some time
until I merge with your changes before committing.

> debug=track causes debug=query info to be suprsedd when no results found
> ------------------------------------------------------------------------
>                 Key: SOLR-6039
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.7
>            Reporter: Hoss Man
>         Attachments: SOLR-6039.patch, SOLR-6039.patch, SOLR-6039.patch
> Shamik Bandopadhyay noted on the mailing list that debugQuery=true wasn't returning info
about how the query was being parsed in SolrCloud.
> Steps to reproduce...
> * startup a simple 2 shard solr cluster using the example configs
> * Load this URL:
> ** http://localhost:8983/solr/select?q=Foo&debug=query
> ** note that the debug=query causes a debug block including "parsedquery" showing "title:foo"
> * Load either of these URLs:
> ** http://localhost:8983/solr/select?q=Foo&debug=query&debug=track
> ** http://localhost:8983/solr/select?q=Foo&debugQuery=true (legacy short hand option
for enabling all debug options)
> ** Note that the debug block exists, but *only* includes the distributed "track" options
- the query parsing debugging info is not available
> * index the sample data (java -jar post.jar *.xml)
> * Load either of these URLs:
> ** http://localhost:8983/solr/select?q=Solr&debugQuery=true&fl=id
> ** http://localhost:8983/solr/select?q=Solr&debug=query&debug=track&fl=id
> ** Note that now we have at least one matching doc, and the parsedquery info is included
in the debug block along with the tracking info
> * Load either of these URLs:
> ** http://localhost:8983/solr/select?q=Solr&debug=query&debug=track&rows=0
> ** http://localhost:8983/solr/select?q=Solr&debug=query&debug=track&rows=0
> ** Note: even though we have a matching doc, since rows=0 prevents it from being returned,
the parsedquery debug info again no longer works - just the track debug info
> ----
> The work around, for people who want don't care about the newer "debug tracking" and
what the same debug information as pre-4.7, is to enumerate the debug options (ie: {{debug=query&debug=timing&debug=results}})
instead of relying on the shorthand: {{debugQuery=true}}

This message was sent by Atlassian JIRA

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

View raw message