On Sun, Oct 11, 2009 at 9:10 AM, Jake Mannix wrote:
> What do you mean "not something I can plug in on top of my original query"?
>
> Do you mean that you can't do it like the more complex example in the class
> you posted earlier in the thread, where you take a linear combination of
> the
> Map
t garbage collected (there's a WeakHashMap in the background), so
> don't accidentally hang onto references to those IndexReaders past
> when needed.
>
Good to know.
>
> -jake
>
> On Fri, Oct 9, 2009 at 3:52 PM, scott w wrote:
>
> > Thanks Jake! I wil
Thanks Jake! I will test this out and report back soon in case it's helpful
to others. Definitely appreciate the help.
Scott
On Fri, Oct 9, 2009 at 3:33 PM, Jake Mannix wrote:
> On Fri, Oct 9, 2009 at 3:07 PM, scott w wrote:
>
> > Example Document:
> > model_1_score
, and then you want to multiply those indexed floats
> by query-time values to make the score?
>
> I'm sorry if I'm not fully following how this works. Can you restate
> your example showing what you have in the index, and what comes
> in in the query?
>
> -jake
>
ing CustomScoreQuery and which
> is usually used with ValueSourceQuery, but you don't use that part, and
> ignore the valSrcScore in your computation.
>
> Where are the parts of your score coming from? The termWeight map
> is used how exactly?
>
> -jake
>
> On Fri
/getting-started-with-payloads/
>>
>> -Grant
>>
>> On Oct 8, 2009, at 11:56 AM, scott w wrote:
>>
>> Oops, forgot to include the class I mentioned. Here it is:
>>>
>>> public class QueryTermBoostingQuery extends CustomScoreQuery {
>>>
hile) that if the terms
> you load are indexed that'll help. But this is mostly
> a guess.
>
> What version of Lucene are you using???
>
> Good luck!
> Erick
>
> On Thu, Oct 8, 2009 at 10:56 AM, scott w wrote:
>
> > Oops, forgot to include the clas
core + (1 - bias) * termWeightedScore;
}
}
On Thu, Oct 8, 2009 at 7:54 AM, scott w wrote:
> I am trying to come up with a performant query that will allow me to use a
> custom score where the custom score is a sum-product over a set of query
> time weights where each weight gets applied only if the
I am trying to come up with a performant query that will allow me to use a
custom score where the custom score is a sum-product over a set of query
time weights where each weight gets applied only if the query time term
exists in the document . So for example if I have a doc with three fields:
comp
