Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Message-ID: <4122528B.5000603@koberg.com>
Date: Tue, 17 Aug 2004 11:46:35 -0700
From: Robert Koberg <rob@koberg.com>
User-Agent: Mozilla Thunderbird 0.7 (Macintosh/20040616)
MIME-Version: 1.0
To: Lucene Developers List <lucene-dev@jakarta.apache.org>
Subject: Re: the future of DateField
References: <200408171735.03548@danielnaber.de>
 <1092764048.7071.31.camel@localhost.localdomain>
 <41224567.8010206@koberg.com> <200408172037.28652@danielnaber.de>
In-Reply-To: <200408172037.28652@danielnaber.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Daniel Naber wrote:

>On Tuesday 17 August 2004 19:50, Robert Koberg wrote:
>
>  
>
>>Why can't Field.Text
>>be used? In other words, why cant the date string be tokenized?
>>    
>>
>
>What would you gain? If you tokenize "2004-08-12" into 2004, 08, 12 you can 
>only find that date with a phrase query, which is slower than a term 
>query. Also, you can search for "12" but you get both documents from 
>December and those from the 12th of any month, which doesn't make sense.
>  
>

It is not a big deal, but forces me to check for the 2 different date 
attributes in the XML I am indexing as opposed to using Field.Text for 
all and not check. I did not realize it uses a dash as the separator. I 
thought dashes were just stripped.

best,
-Rob

>Regards
> Daniel
>
>  
>


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