Re: query issue /special character and case

2009-06-08 Thread revas
On Sat, Jun 6, 2009 at 11:40 AM, Shalin Shekhar Mangar < shalinman...@gmail.com> wrote: > On Sat, May 30, 2009 at 9:48 AM, revas wrote: > > > Hi , > > > > When i give a query like the following ,why does it become a phrase query > > as shown below? > > The field type is the default text field in

Re: query issue /special character and case

2009-06-08 Thread Jay Hill
Regarding being able to search SCHOLKOPF (o with no umlaut) and match SCHÖLKOPF (with umlaut) try using the ISOLatin1AccentFilterFactory in your analysis chain: This filter removes accented chars and replaces them with non-accented versions. As always, make sure to add it to the for both

Re: query issue /special character and case

2009-06-05 Thread Shalin Shekhar Mangar
On Sat, May 30, 2009 at 9:48 AM, revas wrote: > Hi , > > When i give a query like the following ,why does it become a phrase query > as shown below? > The field type is the default text field in the schema. > > volker-blanz > PhraseQuery(content:"volker blanz") > What is the query that was sent