[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kinosearch
Subject:    [KinoSearch] Field search behaviour
From:       henka () cityweb ! co ! za (Henka)
Date:       2006-11-24 6:27:30
Message-ID: 63596.196.23.181.69.1164377791.squirrel () support ! metroweb ! co ! za
[Download RAW message or body]



>
> On Nov 24, 2006, at 4:07 AM, Henka wrote:
>> When searching:
>>
>> field1:cat +dog
>>
>> I notice that the behaviour becomes:
>>
>> field1 'should' contain cat, and any field 'must' contain dog.
>>
>> In order to simulate google's site:www.abc.com search behaviour, I
>> presume
>> one would have to change the above to:
>>
>> +field1:cat +dog
>
> That's necessary but not sufficient.  Under the default Tokenizer,
> site:www.abc.com translates to...
>
> site:www site:abc site:com

understood.

> If you use a custom Tokenizer that keeps those together, that helps.
> But you also need to make preparations at index-time, because
> Google's 'site:' feature allows you to search subdomains and
> subdirectories.

I defined the 'site' field as being indexed, but not analyzed.  Does that
mean the field contents is not parsed/tokenised into bits (for searching),
or does defining the field as indexed also imply parsing/tokenising?


[prev in list] [next in list] [prev in thread] [next in thread]