The debugQuery parameter shows you how the query is parsed into a tree of Lucene query objects.
http://wiki.apache.org/solr/CommonQueryParameters#debugQuery On Wed, Feb 3, 2010 at 3:40 PM, Simon Wistow <si...@thegestalt.org> wrote: > According to my logs > > org.apache.solr.handler.component.QueryComponent.process() > > takes a significant amount of time (>5s but I've seen up to 15s) when a > query has an odd pattern of numbers in e.g > > "neodymium megagauss-oersteds (MGOe) (1 MG·Oe = 7,958·10³ T·A/m = 7,958 > kJ/m³" > > "myers 8e psychology chapter 9" > > "JOHN PIPER 1 TIMOTEO 3:1? > > "lab 2.6.2: using wireshark to view protocol data units" > > "malha de aço 3x3 6mm - peso m2" > > or even looks like it could be a query > > "An experiment has two outcomes, A and A. If A is three time as likely to > occur as , what is P(A)?" > > other params were > > fl: > *,score > fq: > +num_pages:[2 TO *] AND +language:1 > hl: > true > hl.fl: > content title description > hl.simple.post: > </strong> > hl.simple.pre: > <strong> > hl.snippets: > 2 > qf: > title^1.5 content^0.8 > qs: > 2 > qt: > dismax > rows: > 10 > sort: > score desc > start: > 0 > wt: > json > > > is this just something I'm going to have to put up with? Or is there > something I can do to mitigate it. If it's a bug any suggestions on how > to start patching it? > > > -- Lance Norskog goks...@gmail.com
