On Friday 02 April 2004 23:48, Erik Hatcher wrote:
On Apr 2, 2004, at 10:00 AM, [EMAIL PROTECTED] wrote:
On Saturday 13 March 2004 11:06, Otis Gospodnetic wrote:
Field.Keyword is suitable for storing data like Url. Give that a try.
I just tried this a minute ago and found that I cannot
On Apr 3, 2004, at 3:19 AM, [EMAIL PROTECTED] wrote:
You *can* use wildcards with keywords (in fact, a keyword really has
no
meaning once indexed - everything is a term at that point).
Well, I just tried. I also was surprised actually - but it just
didn't work.
I can use wildcards for
On Saturday 03 April 2004 11:48, Erik Hatcher wrote:
Provide us the results of running your url through that, using the same
SnowballAnalyzer(German2):
Analzying http://www.yahoo.com/foo/bar.html;
org.apache.lucene.analysis.WhitespaceAnalyzer:
Ok, we're getting somewhere now.
So, where is the exception you encountered when using this utility
code?! (i.e. it didn't thrown an exception, so something is different
in your usage in your code).
I tried this:
Query query = MultiFieldQueryParser.parse(date:[20030101 TO
20030202], new
On Saturday 03 April 2004 15:19, Erik Hatcher wrote:
date:[20030101 TO 20030202]
I found the/my bug.
Since Lucene is case-sensitive, I do lower-case all queries for user's
convenience. The ParseException is thrown because the TO becomes to.
Well, I really think Lucene needs to daff such
On Apr 3, 2004, at 9:59 AM, [EMAIL PROTECTED] wrote:
On Saturday 03 April 2004 15:19, Erik Hatcher wrote:
date:[20030101 TO 20030202]
I found the/my bug.
Since Lucene is case-sensitive, I do lower-case all queries for user's
convenience. The ParseException is thrown because the TO becomes
to.
On Saturday 03 April 2004 17:11, Erik Hatcher wrote:
No objections that error messages and such could be made clearer.
Patches welcome! Care to submit better error message handling in this
case? Or perhaps allow lower-case to?
I think the best would be if Lucene would simply have a
On Apr 3, 2004, at 10:34 AM, [EMAIL PROTECTED] wrote:
I forgot that I did lower-case it. I fact I even output it in it's
original
state but lower-case it just before I pass it to lucene. That
lower-casing is
what I would call a hack and hence it's no surprise that I forgot it
:-)
But why even
On Saturday 03 April 2004 08:34, [EMAIL PROTECTED] wrote:
On Saturday 03 April 2004 17:11, Erik Hatcher wrote:
No objections that error messages and such could be made clearer.
Patches welcome! Care to submit better error message handling in this
case? Or perhaps allow lower-case to?
I
Extremely well said, Tatu!
On Apr 3, 2004, at 11:24 AM, Tatu Saloranta wrote:
On Saturday 03 April 2004 08:34, [EMAIL PROTECTED] wrote:
On Saturday 03 April 2004 17:11, Erik Hatcher wrote:
No objections that error messages and such could be made clearer.
Patches welcome! Care to submit better
On Saturday 13 March 2004 11:06, Otis Gospodnetic wrote:
Field.Keyword is suitable for storing data like Url. Give that a try.
I just tried this a minute ago and found that I cannot use wildcards with
Keywords: url:www.yahoo.*
On Apr 2, 2004, at 10:00 AM, [EMAIL PROTECTED] wrote:
On Saturday 13 March 2004 11:06, Otis Gospodnetic wrote:
Field.Keyword is suitable for storing data like Url. Give that a try.
I just tried this a minute ago and found that I cannot use wildcards
with
Keywords: url:www.yahoo.*
You *can* use
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 13, 2004 3:14 AM
To: Lucene Users List
Subject: Re: Zero hits for queries ending with a number
On Mar 13, 2004, at 6:02 AM, Morus Walter wrote:
Otis Gospodnetic writes:
Field.Keyword is suitable
On Mar 24, 2004, at 5:58 PM, Morris Mizrahi wrote:
I think the custom analyzer I created is not properly doing what a
KeywordAnalyzer would do.
Erik, could you please post what KeywordAnalyzer should look like?
It should simply tokenize the entire input as a single token. Incze
Lajos posted a
To: Lucene Users List
Subject: Re: Zero hits for queries ending with a number
On Mar 24, 2004, at 5:58 PM, Morris Mizrahi wrote:
I think the custom analyzer I created is not properly doing what a
KeywordAnalyzer would do.
Erik, could you please post what KeywordAnalyzer should look like?
It should
On Mar 13, 2004, at 6:02 AM, Morus Walter wrote:
Otis Gospodnetic writes:
Field.Keyword is suitable for storing data like Url. Give that a try.
Hmm. I don't think keyword fields can be used with query parser,
which is probably one of the problems here.
He did try keyword fields.
Look in the
16 matches
Mail list logo
