Re: Strange change to query parser behaviour in recent versions

2011-08-21 Thread Trejkaz
On Sat, Aug 20, 2011 at 7:00 PM, Robert Muir wrote: > On Sat, Aug 20, 2011 at 3:34 AM, Trejkaz wrote: > >> >> As an aside, Google's behaviour seems to follow the "old" way.  For >> instance, [[ 限定 ]] returns 640,000,000 hits and [[ 限 定 ]] returns >> 772,000,000.  (Interestingly, [[ "限定" ]] return

Re: Strange change to query parser behaviour in recent versions

2011-08-20 Thread Robert Muir
On Sat, Aug 20, 2011 at 3:34 AM, Trejkaz wrote: > > As an aside, Google's behaviour seems to follow the "old" way.  For > instance, [[ 限定 ]] returns 640,000,000 hits and [[ 限 定 ]] returns > 772,000,000.  (Interestingly, [[ "限定" ]] returns 643,000,000 hits. > Slightly more than you might expect.)

Re: Strange change to query parser behaviour in recent versions

2011-08-20 Thread Trejkaz
On Fri, Aug 19, 2011 at 11:05 AM, Chris Hostetter wrote: > > See LUCENE-2458 for the backstory. > > the argument was that while phrase queries were historicly generated by > the query parser when a single (white space deliminated) "chunk" of query > parser input produced multiple tokens, that logi

Re: Strange change to query parser behaviour in recent versions

2011-08-18 Thread Chris Hostetter
See LUCENE-2458 for the backstory. the argument was that while phrase queries were historicly generated by the query parser when a single (white space deliminated) "chunk" of query parser input produced multiple tokens, that logic didn't make sense in CJK type langauges where whitespace is not