Hi Erick,

I'll try without the type="index" on analyzer tag and then I'll
re-index some files.

Thanks for you answer.

On Thu, Oct 27, 2011 at 6:54 PM, Erick Erickson <erickerick...@gmail.com> wrote:
> Hmmm, I'm not sure what happens when you specify
> <analyzer> (without type="index" and
> <analyzer type="query">. I have no clue which one
> is used.
>
> Look at the admin/analysis page to understand how things are
> broken up.
>
> Did you re-index after you added the ngram filter?
>
> You'll get better help if you include example queries with
> &debugQuery=on appended, it'll give us a lot more to
> work with.
>
> Best
> Erick
>
> On Wed, Oct 26, 2011 at 4:14 PM, Boris Quiroz <boris.qui...@menco.it> wrote:
>> Hi,
>>
>> I've solr running on a CentOS server working OK, but sometimes my 
>> application needs to index some parts of a word. For example, if I search 
>> 'dislike' word fine but if I search 'disl' it returns zero. Also, if I 
>> search 'disl*' returns some values (the same if I search for 'dislike') but 
>> if I search 'dislike*' it returns zero too.
>>
>> So, I've two questions:
>>
>> 1. How exactly the asterisk works as a wildcard?
>>
>> 2. What can I do to index properly parts of a word? I added this lines to my 
>> schema.xml:
>>
>> <fieldType name="text" class="solr.TextField" omitNorms="false">
>>      <analyzer>
>>        <tokenizer class="solr.StandardTokenizerFactory"/>
>>        <filter class="solr.StandardFilterFactory"/>
>>        <filter class="solr.LowerCaseFilterFactory"/>
>>        <filter class="solr.NGramFilterFactory" minGramSize="2" 
>> maxGramSize="15"/>
>>      </analyzer>
>>
>>      <analyzer type="query">
>>        <tokenizer class="solr.StandardTokenizerFactory"/>
>>        <filter class="solr.StandardFilterFactory"/>
>>        <filter class="solr.LowerCaseFilterFactory"/>
>>      </analyzer>
>> </fieldType>
>>
>> But I can't get it to work. Is OK what I did or I'm wrong?
>>
>> Thanks.
>>
>> --
>> Boris Quiroz
>> boris.qui...@menco.it
>>
>>
>



-- 
Boris Quiroz
boris.qui...@menco.it

Reply via email to