gards,
> Raghu
>
>
> -Original Message-
> From: Rao, Raghavendra: IT (NYK)
> Sent: Sunday, November 17, 2013 12:54 PM
> To: java-user@lucene.apache.org
> Subject: RE: WhitespaceAnalyzer vs StandardAnalyzer
>
> The solution clicked to me as soon as I sent the e
:54 PM
To: java-user@lucene.apache.org
Subject: RE: WhitespaceAnalyzer vs StandardAnalyzer
The solution clicked to me as soon as I sent the email :)
The problem was that I was enclosing the search text with double quotes (for
PhraseQuery) before providing it to QueryParser and it was getting messed up
tSearchString.toUpperCase()) + "\"");
Regards,
Raghu
-Original Message-
From: Rao, Raghavendra: IT (NYK)
Sent: Sunday, November 17, 2013 12:36 PM
To: java-user@lucene.apache.org
Subject: RE: WhitespaceAnalyzer vs StandardAnalyzer
Thank you very much, Eric.
WhitespaceAnalyzer
om: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Friday, November 15, 2013 4:45 PM
To: java-user
Subject: Re: WhitespaceAnalyzer vs StandardAnalyzer
Well, your example will work exactly as you want. And if your input is strictly
controlled, that's fine. But if you're putting in
Hi,
whitespace analyzer would be ideal for your requirement.
On Sat, Nov 16, 2013 at 1:51 AM, wrote:
> Hi,
>
> I implemented my Lucene solution using StandardAnalyzer for both indexing
> and searching. While testing, I noticed that special characters such as
> hyphens, forward slash etc. are o
Well, your example will work exactly as you want. And if your input is
strictly controlled, that's fine. But if you're putting in text, for
instance, punctuation will be part of the token. I.e. in the sentence just
before this one, "token" would not be found, but "token." would.
The admin/analysi
Hi,
I implemented my Lucene solution using StandardAnalyzer for both indexing and
searching. While testing, I noticed that special characters such as hyphens,
forward slash etc. are omitted by this Analyzer.
In plain English, the requirement is to search for individual words, in Lucene
terms S
