Append &debugQuery=true to your query.
It isn't exactly like a SQL execution plan but will give you the details of
how the query was parsed, scored and how much time was taken by each module
used by the request handler.

On Mon, 15 Feb 2016, 10:42 Shahzad Masud <
shahzad.ma...@northbaysolutions.net> wrote:

> Please pardon my ignorance, but just wanted to check if there is anything
> like explain plan while executing query on Solr. I have one query which is
> taking a lot of time (56-68 seconds) with very huge network activity. While
> most of queries are taking less than 4 seconds.
>
>
> {!surround}<Contents:~(25,^(5,|("personal","private"),^(10,"loan",~(25,|("master*","chef*"),|(^(1,"american",^(1,"idol","samir")),|("ocean",|("eleven",|("ocean*","twelve*"))))))),|(^(1,"you","see*"),|("me!",|("nine",|("ten",|(^(2,"eleven","twelve"),|("pirates*","carribean")))))))>
>
> I have masked all text values in the query, while real values does exists
> separately resulting in around 10-300 msec.
>
>
> {!surround}<Contents:&(~(5,"test","milestone"),&(~(5,"benstock",|("monumental","dinner")),"highway"))>
> = returning in almost 10 msec
>
> Shahzad
>
-- 
Regards,
Binoy Dalal

Reply via email to