What it probably boils down to is how you analyzed (or didn't) those fields.

What is your schema for those fields?

        Erik


On Apr 25, 2007, at 4:40 PM, Michael Kimsal wrote:

leading and trailing at the same time don't work. :( This is supposedly fixed in a lucene nightly, but I can't get solr and lucene trunks to compile together. Also, I wouldn't be able to convince anyone here to run nightly
trunks in production.  :)



On 4/25/07, Walter Underwood <[EMAIL PROTECTED]> wrote:

Enable leading wildcards and try this:

type:changelog AND filename:*angel*

wunder

On 4/25/07 1:34 PM, "Michael Kimsal" <[EMAIL PROTECTED]> wrote:

> Thanks. I'm still no results with your suggestion though. I also tried
>
> type:+changelog AND ( (filename:angel) OR (filename:angel*)  OR
> (filename:*angel) )
>
> but am getting parse errors.  :(
>
>
> On 4/25/07, Cody Caughlan <[EMAIL PROTECTED]> wrote:
>>
>> What about:
>>
>> (type:changelog) AND (filename:angel)
>>
>> Or if you do the 3 different type of filename queries, use parenthesis
>> to properly break them up, e..g
>>
>> type:changelog AND (filename:... OR filename:... OR filename:...)
>>
>> I dont know enough about how Lucene's precedence rules, but you might
>> have better luck with this kind of grouping.
>>
>> /cody
>>
>> On 4/25/07, Michael Kimsal <[EMAIL PROTECTED]> wrote:
>>> Hello all:
>>>
>>> I'm trying to find a record in my index where the 'type' is changelog
>> and
>>> the 'filename' has 'angel' in it.
>>>
>>> Expressing this as
>>> type:changelog filename:+angel or filename:+angel* or filename: +*angel
>>>
>>> throws a parse error (probably understandably)
>>>
>>> type:changelog (filename:+angel or filename:+angel* or
filename:+*angel)
>>> doesn't seem to work either.
>>>
>>> I've tried this a number of ways and I either get a parse error or
>>> *everything* is returned - I only want
>>> records where the type is 'changelog' and the filename has 'angel' in
>> it.
>>> How would this be expressed?
>>>
>>>
>>> --
>>> Michael Kimsal
>>> http://webdevradio.com
>>>
>>
>
>




--
Michael Kimsal
http://webdevradio.com

Reply via email to