I've used Luke to figure out what is going on, and I see in the fields that fail to match, a "null_1". Could someone tell me what that is? I see some null_100s there as well, which see to separate field values. Clearly the null_1s are causing the search to fail.
--peter keane On Mon, Aug 3, 2009 at 2:56 PM, Peter Keane <pke...@mail.utexas.edu> wrote: > Greetings-- > > I am having a problem with a search that has stumped me. I have a field > (called "source") with the following value: > > Miguel : three dimensions : [Exhibition] > > when I perform this search: > > source:"Miguel \: three dimensions \: \[Exhibition\]" > > it fails to match. > > Yet when I change the value to: > > Miguel : three dimensions : [Exhibitio > > the following search matches: > > source:"Miguel \: three dimensions \: \[Exhibitio" > > This is a text field type w/ schema.xml: > > <fieldType name="text" class="solr.TextField" positionIncrementGap="100"> > > <analyzer type="index"> > <tokenizer class="solr.WhitespaceTokenizerFactory"/> > <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" > generateNumberParts="1" catenateWords="1" catenateNumbers="1" > catenateAll="0" splitOnCaseChange="1"/> > <filter class="solr.LowerCaseFilterFactory"/> > </analyzer> > > <analyzer type="query"> > <tokenizer class="solr.WhitespaceTokenizerFactory"/> > <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" > generateNumberParts="1" catenateWords="0" catenateNumbers="0" > catenateAll="0" splitOnCaseChange="1"/> > <filter class="solr.LowerCaseFilterFactory"/> > </analyzer> > > </fieldType> > > I've tried lots of variations with combinations of characters that require > escaping and have not found a pattern as to why it sometimes works and > sometimes not. (Note the quotations marks -- these are phrase searches). I > had other problems that kep me from using a string tye for these fields. > > --peter keane >
