Skip to main content.
home | support | download

Back to List Archive

Re: NOT just plain broken for me.

From: Peter Karman <peter(at)not-real.peknet.com>
Date: Fri Feb 11 2005 - 23:17:33 GMT
Orange County + rain? that's pretty rare, if I remember my boyhood.

I assume you have job defined as a metaname.

did you also alias job to swishdefault?

check out the metanamealias config, if you haven't already.

not sure if that's related, but I'm grasping.

Mark Maunder wrote on 2/11/05 3:47 PM:
> I'm afraid California is horrible today. Orange County is rainy and
> windy and just plain yuck. 
> 
> I'm indexing XML like so:
> <job>
> <title>Some title</title>
> <body>Some body text and more and more</body>
> </job>
> 
> The query is job=(keywords)
> 
> Not sure if that affects things. 
> 
> On Fri, 2005-02-11 at 15:41 -0600, Peter Karman wrote:
> 
>>Bill will likely correct me here; here's my guess.
>>
>>since the default metaname is 'swishdefault' and all words not otherwise 
>>assigned to a metaname are indexed there, perhaps the query parser is doing 
>>something like:
>>
>>swishdefault=ceo and swishdefault=(not assistant)
>>
>>which would explain why your first example doesn't behave as expected (assuming 
>>that the 'assistant' in the title is not indexed under swishdefault).
>>
>>there are no default stopwords, however -- unless you are using IgnoreLimit ? -- 
>>so that doesn't explain your last example (the presence of 'the').
>>
>>Bill will need to weigh in, if he isn't out enjoying the California sunshine.
>>
>>
>>
>>Mark Maunder wrote on 2/11/05 3:33 PM:
>>
>>>Some tests with the phrases before the dash in the parentheses:
>>>
>>>ceo not assistant - brings back jobs with assistant in the title
>>>ceo - works fine
>>>not assistant - brings back 220,000 out of a possible 233,000 which
>>>sounds about right.
>>>ceo not ceo - brings back nothing as expected
>>>ceo not the - brings back jobs with the in the body text. Is it a
>>>default stopword? Just guessing here. 
>>>
>>>
>>>
>>>On Fri, 2005-02-11 at 15:25 -0600, Peter Karman wrote:
>>>
>>>
>>>>does
>>>>
>>>>'job=(ceo) and job=(not assistant)'
>>>>
>>>>also fail?
>>>>
>>>>Mark Maunder wrote on 2/11/05 3:22 PM:
>>>>
>>>>
>>>>>Gulp. My mistake. Not appears to be completely broken for me.
>>>>>RankScheme(0) just moved the erroneous results further down the pile.
>>>>>Has anyone else experienced a broken NOT when indexing XML and using
>>>>>MetaNames to query?
>>>>>
>>>>>Thanks.
>>>>>
>>>>>On Fri, 2005-02-11 at 13:09 -0800, Mark Maunder wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>Firstly tip of the hat to the swish team - the new site rocks, and as
>>>>>>usual so does the little miracle that it supports. 
>>>>>>
>>>>>>I'm indexing using XML with metanames and
>>>>>>IgnoreTotalWordCountWhenRanking no
>>>>>>So when I do a query I'll do something like:
>>>>>>job=(CEO not assistant)
>>>>>>
>>>>>>It looks like NOT is not notting when using RankScheme(1). I'm switching
>>>>>>back to RankScheme(0) for now but I'm going to miss RankScheme(1)
>>>>>>because the sizes of the chunks of text that I index vary wildly and I
>>>>>>find that the larger chunks float to the top with (0). 
>>>>>>
>>>>>>Regards,
>>>>>>
>>>>>>Mark.
>>>>>>
>>>>>>
>>>>>>
>>>>

-- 
Peter Karman  .  http://peknet.com/  .  peter(at)not-real.peknet.com
Received on Fri Feb 11 15:17:39 2005