Hi Dan,
Yes, you're right - in fact that was precisely what I was thinking of
doing! Also looking at SOLR-1298 & SOLR-1566 - which would be good for
applying functions generically rather than on a per-use-case basis.
Thanks!
Peter
On Thu, Mar 10, 2011 at 3:58 PM, dan sutton wrote:
> As a worka
As a workaround can you not have a search component run after the
querycomponent, and have the qty_ordered,unit_price as stored fields
and returned with the fl parameter and have your custom component do
the calc, unless you need to sort by this value too?
Dan
On Wed, Mar 9, 2011 at 10:06 PM, Pet
There is a ticket:
https://issues.apache.org/jira/browse/SOLR-1298
On Thursday 10 March 2011 15:46:55 Peter Sturge wrote:
> Hi Markus,
>
> Thanks for your input. Hmmm, so it sounds like all those nice math
> functions operate only on the Lucene tf/idf score.
> In the link you gave, there is ment
Not at the moment if i'm not mistaken. The same issue is with Solr 3.1 where
relative distances are not being returned as field value when doing spatial
filtering. To retrieve the value one must use the score as the some pseudo
field.
http://wiki.apache.org/solr/SpatialSearch#Returning_the_dist
