Re: problem with Whitespace analyzer

2008-02-10 Thread saikrishna venkata pendyala
Hi, Thanks a lot Cohen and Erik. Yes "\)" works, I tried it even before. But I was wondering why the Whitespace analyzer is breaking the string at "(". Now it's clear, thnks once again. --Saikrishna. On Feb 10, 2008 9:17 PM, Erik Hatcher <[EMAIL PROTECTED]> wrote: > QueryParser uses special sy

Re: problem with Whitespace analyzer

2008-02-10 Thread Erik Hatcher
QueryParser uses special syntax, which can get in the way, for operators and grouping, etc. Parenthesis are part of that special syntax, and need to be backslash escaped for QueryParser to skip treating them as grouping operators, for example: Ajit_\(Agarkar\) Erik On Feb 10, 20

Re: problem with Whitespace analyzer

2008-02-10 Thread Doron Cohen
Should be the parenthesis which are part of the query syntax Try escaping - \( \) Also see http://lucene.apache.org/java/2_3_0/queryparsersyntax.html#Escaping%20Special%20Characters Doron On Sun, Feb 10, 2008 at 9:03 AM, saikrishna venkata pendyala < [EMAIL PROTECTED]> wrote: > Hi, > > I am fa

problem with Whitespace analyzer

2008-02-09 Thread saikrishna venkata pendyala
Hi, I am facing a small problem, some one please help me, I am using Whitespace analyzer, while both indexing and searching the files. While indexing the analyzer is recognizing Ajit_(Agarkar)(I found it using LUKE) as a single token. But while searching{QueryParser parser = new QueryParser(fiel

Fw: Urgent : Specific search problem with whitespace analyzer

2006-11-21 Thread Krishnendra Nandi
Hi, I am doing "field:text" kind of search using my own analyzer which behaves like whitespaceanalyzer. Following are the code snippets for my own whitespaceanalyzer and whitespacetokenizer. // WhiteSpaceAnalyzerMaestro.java package com.hewitt.itk.maestro.support.service.simplesearch; import

Re: Fw: Urgent : Specific search problem with whitespace analyzer

2006-11-21 Thread Chris Hostetter
: I have modified the tokenizer class by making it return characters in : lower case. there is really no reason to do this ... have your analyzer use the WhitespaceTokenizer, wrapped in a LowerCaseFilter ... that will illiminate some of your custom code, and perhaps some of your problems as well.