Raav,
You may need to actually subscribe to the solr-user list. Nabble seems to
not be working to well.
p.s. I’m on vacation this week so I can’t be very responsive
First of all... it's not clear you actually want to *boost* (since you seem
to not care about the relevancy score), it seems you want to *sort* based on
a function query. So simply sort by the function query instead of using the
'bq' param.
Have you read about geodist() in the Solr Reference Guide? It returns the
spatial distance. With that and other function queries like map() you could
do something like sum(map(geodist(),0,40,40,0),map(geodist(),0,20,10,0)) and
you could put that into your main function query. I purposefully overlapped
the map ranges so that I didn't have to deal with double-counting an edge.
The only thing I don't like about this is that the distance is going to be
calculated as many times as you reference the function, and it's slow. So
you may want to write your own function query (internally called a
ValueSource), which is relatively easy to do in Solr.
~ David
sraav wrote
> David,
>
> Thank you for your prompt response. I truly appreciate it. Also, My post
> was not accepted the first two times so I am posting it again one final
> time.
>
> In my case I want to turn off the dependency on scoring and let solr use
> just the boost values that I pass to each function to sort on. Here is a
> quick example of how I got that to work with non-geo fields which are
> present in the document and are not dynamically calculated. Using edismax
> ofcourse.
>
> I was able to turn off the scoring (i mean remove the dependency on score)
> on the result set and drive the sort by the boost that I mentioned in the
> below query. In the below function For example - if the "document1"
> matches the date listed it gets a boost = 5. If the same document matches
> the owner AND product - it will get an additional boost of 5 more. The
> total boost of this "document1" is 10. From what ever I have seen, it
> seems like i was able to turn off of negate the affects of solr score.
> There was a query norm param that was affecting the boost but it seemed to
> be a constant around 0.70345...most of the time for any fq mentioned).
>
> bq = {!func}sum(if(query({!v='datelisted:[2015-01-22T00:00:00.000Z TO
> *]'}),5,0),if(and(query({!v='owner:*BRAVE*'}),query({!v='PRODUCT:*SWORD*'}),5,0))
>
> What I am trying to do is to add additional boosting function to the
> custom boost that will eventually tie into the above function and boost
> value.
>
> For example - if "document1" falls in 0-20 KM range i would like to add a
> boost of 50 making the final boost value to be 60. If it falls under
> 20-40KM - i would like to add a boost of 40 and so on.
>
> Is there a way we can do this? Please let me know if I can provide better
> clarity on the use case that I am trying to solve. Thank you David.
>
> Thanks,
> Raav
-----
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
Independent Lucene/Solr search consultant,
http://www.linkedin.com/in/davidwsmiley
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boosting-by-calculated-distance-buckets-tp4186504p4187112.html
Sent from the Solr - User mailing list archive at Nabble.com.
