Re: search behavior on a case-sensitive field

2012-12-03 Thread Joe Zhang
haha, makes perfect sense! Thanks a lot! On Mon, Dec 3, 2012 at 9:25 PM, Jack Krupansky wrote: > "CoSt" was split into two terms and the query parser generated an OR of > them. Adding the autoGeneratePhraseQueries="**true" attribute to your > field type should fix the problem. > > You can also ch

Re: search behavior on a case-sensitive field

2012-12-03 Thread Jack Krupansky
"CoSt" was split into two terms and the query parser generated an OR of them. Adding the autoGeneratePhraseQueries="true" attribute to your field type should fix the problem. You can also change splitOnCaseChange="1" to splitOnCaseChange="0" to avoid the term splitting issue. Be sure to comp