The stopwords stanza looks like:
<filter class="solr.StopFilterFactory"
ignoreCase="true"
words="stopwords.txt"
enablePositionIncrements="true"
/>
Which is the same as the example schema
http://svn.apache.org/repos/asf/lucene/solr/branches/branch-1.4/example/solr/conf/schema.xml
changing this to enablePositionIncrements="false" seems to make the
searching work as expected. Is it incorrect to have that directive
here, or is this a bug?
-Peter
On Sat, Mar 27, 2010 at 4:25 PM, Peter Wolanin <peter.wola...@acquia.com> wrote:
> The output on the analysis screen does look correct. Here are 2 screen shots:
>
> empty stopwords: http://img.skitch.com/20100327-rcsjdih4bn3y8ahajqa5wjwybd.png
>
> standard stopwords:
> http://img.skitch.com/20100327-1w5ct1wr25jkir4sji8kumefn1.png
>
> -Peter
>
> On Sat, Mar 27, 2010 at 4:13 PM, MitchK <mitc...@web.de> wrote:
>>
>> Peter,
>>
>> if you are right, please outcomment the stopword filter to make clear, that
>> the problem is really a problem of how the stopword filter deletes
>> stopwords.
>>
>> Is the output correct, if you enter "would be great to have support for
>> Identi.ca on the follow block" in the query-label at the analysis.jsp? Can
>> you make a screenshot for this sentence?
>>
>> - Mitch
>> --
>> View this message in context:
>> http://n3.nabble.com/Solr-1-4-bug-search-fails-but-analyzer-indicates-a-match-tp680066p680530.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> Peter M. Wolanin, Ph.D.
> Momentum Specialist, Acquia. Inc.
> peter.wola...@acquia.com
>
--
Peter M. Wolanin, Ph.D.
Momentum Specialist, Acquia. Inc.
peter.wola...@acquia.com
