On Thu, Nov 12, 2009 at 3:00 PM, Stephen Duncan Jr wrote:
> On Thu, Nov 12, 2009 at 2:54 PM, Chris Hostetter > wrote:
>
>>
>> oh man, so you were parsing the Stored field values of every matching doc
>> at query time? ouch.
>>
>> Assuming i'm understanding your goal, the conventional way to solv
On Thu, Nov 12, 2009 at 2:54 PM, Chris Hostetter
wrote:
>
> oh man, so you were parsing the Stored field values of every matching doc
> at query time? ouch.
>
> Assuming i'm understanding your goal, the conventional way to solve this
> type of problem is "payloads" ... you'll find lots of discussi
: Here's how we did it in Lucene: we had an extension of Query, with a custom
: scorer. In the index we stored the category id's as single-valued
: space-separated string. We also stored a space-separated string of scores
: in another field. We made of these fields stored. We simply delegated
We've had a customized score calculator for one of our fields that we
developed when we were using Lucene instead of Solr (lucene 2.4). During
our switch to Solr, we simply continued to use that code. However, as the
version of Lucene used in Solr changed to 2.9, somewhere along the way
(unfortun
