Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <013e01c44e20$cf777910$6501a8c0@POWERPACK>
References: <40C6C9C9.9010005@healthonnet.org>
 <E8CF4596-BA08-11D8-9C12-000393A564E6@ehatchersolutions.com>
 <013e01c44e20$cf777910$6501a8c0@POWERPACK>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <78244575-BA1A-11D8-A592-000393A564E6@ehatchersolutions.com>
Content-Transfer-Encoding: 7bit
From: Erik Hatcher <erik@ehatchersolutions.com>
Subject: Re: Proximity Searches  behavior
Date: Wed, 9 Jun 2004 09:39:45 -0400
To: "Lucene Users List" <lucene-user@jakarta.apache.org>

On Jun 9, 2004, at 8:53 AM, Terry Steichen wrote:
> 3) Is there a plan for adding QueryParser support for the SpanQuery 
> family?

Another important facet to Terry's question here is what syntax to use 
to express all various types of queries?  I suspect that Google stats 
show us that most folks query with 1 - 3 words and do not use the any 
of the advanced features.

The elegance of the query syntax is quite important, and QueryParser 
has gotten a bit hairy.  I would enjoy discussions on creating new 
query parsers (one size doesn't fit all, I don't think) and what syntax 
should be used.

Paul Elschot created a "surround" query parser that he posted about to 
the list in April.

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org