Not sure, but it sounds like you are interested in a higher level
Query, kind of like the BooleanQuery, but then part of it sounds like
it is per document, right? Is it that you want to deal with multiple
payloads in a document, or multiple BTQs in a bigger query?
On Nov 4, 2008, at 9:42 AM
Let me give some background on the problem behind my question.
Our index contains many fields (title, body, date, city, etc). Most queries
search all fields, but for best performance, we create an additional
'contents' field that contains all terms from all fields so that only one
field needs to b
I've discovered another flaw in using this technique:
(+contents:petroleum +contents:engineer +contents:refinery)
(+boost:petroleum +boost:engineer +boost:refinery)
It's possible that the first clause will produce a matching doc and none of
the terms in the second clause are used to score that do
Hi Peter,
On 11/06/2008 at 4:25 PM, Peter Keegan wrote:
> I've discovered another flaw in using this technique:
>
> (+contents:petroleum +contents:engineer +contents:refinery)
> (+boost:petroleum +boost:engineer +boost:refinery)
>
> It's possible that the first clause will produce a matching
> d
boost:(+petroleum +engineer +refinery)
(+contents:(+petroleum +engineer +refinery)
+((*:* -boost:petroleum)
(*:* -boost:engineer)
(*:* -boost:refinery)))
That's an interesting solution. Would this result in many more documents
being visited by the scorer, possibly impacting performance
