On Wed, Feb 03, 2010 at 07:38:13PM -0800, Lance Norskog said: > The debugQuery parameter shows you how the query is parsed into a tree > of Lucene query objects.
Well, that's kind of what I'm asking - I know how the query is being parsed: <str name="rawquerystring">myers 8e psychology chapter 9</str> <str name="querystring">myers 8e psychology chapter 9</str> <str name="parsedquery"> +((DisjunctionMaxQuery((content:myer^0.8 | title:myer^1.5)~0.01) DisjunctionMaxQuery((content:"8 e"~2^0.8 | title:"8 e"~2^1.5)~0.01) DisjunctionMaxQuery((content:psycholog^0.8 | title:psycholog^1.5)~0.01) DisjunctionMaxQuery((content:chapter^0.8 | title:chapter^1.5)~0.01) DisjunctionMaxQuery((content:9^0.8 | title:9^1.5)~0.01))~4) () </str> <str name="parsedquery_toString"> +(((content:myer^0.8 | title:myer^1.5)~0.01 (content:"8 e"~2^0.8 | title:"8 e"~2^1.5)~0.01 (content:psycholog^0.8 | title:psycholog^1.5)~0.01 (content:chapter^0.8 | title:chapter^1.5)~0.01 (content:9^0.8 | title:9^1.5)~0.01)~4) () </str> But that's sort of besides the point - I was really asking if this is a known issue (i.e queries with numbers in them can be very slow) and whether there are any workarounds
