Return-Path: Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 15972 invoked from network); 9 Oct 2001 15:57:55 -0000 Received: from rlf2.demon.co.uk (194.222.38.235) by daedalus.apache.org with SMTP; 9 Oct 2001 15:57:55 -0000 Received: from murphy.granta.internal (murphy) [10.0.0.36] by rlf2.demon.co.uk with smtp (Exim 3.12 #1 (Debian)) id 15qzGP-0004Om-00; Tue, 09 Oct 2001 16:57:49 +0100 Message-ID: <010101c150db$253d0360$2400000a@trumpton.internal> From: "Lee Mallabone" To: References: <4BC270C6AB8AD411AD0B00B0D0493DF0EE7C40@mail.grandcentral.com> Subject: Re: context and hit positions with Lucene Date: Tue, 9 Oct 2001 16:57:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Doug Cutting wrote: > Phrase slop is thus essentially WITHIN. The queryParser class does not yet > have a syntax to specify slop. Are there any short term plans to extend the queryParser to handle this? > One could of course write a > TokenStream-based query evaluator that correctly interpreted phrasal > restrictions when highlighting. Personally, I do not think it is worth the > effort, so I am not volunteering to do it myself. I'd be very inclined to agree with you. :) Cheers, Lee Mallabone.