OK lets for a moment forget about this specific use case and consider a more general case. Lets say the field name is "keywords" are we are storing text in it, query is of the type "keywords:(word1 OR word2 ... OR wordN)". The client is relying on default relevancy based sort returned by solr. Some documents can get penalised because of some other documents which were deleted. Is this functionality correct?
On Wed, Jun 18, 2014 at 12:52 AM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : Currently we are not using SolrJ but are simply interacting with solr > with > : json over http, this will change in a couple of months but currently not > : there. As of now we are putting all the logic in query building, using it > : to query solr and then passing on the json returned by it to front end. I > : know this is not the ideal approach, but that's what we have at the > moment. > : Hence need a way of deterministically order the result set provided they > : match other search criteria. > > wether you are using SOlrJ or not doesn't really change my point at all -- > you are jumping though all sorts of hoops, and asking solr to jump through > all sorts of hoops, for a score you don't actaully care about, and isn't > going ot work perfectly for what you want anyway because of the > fundemental nature of the inverted index stats, leading you to look for > even smaller, higher, hoops to try and jump through. > > it would be far simpler to just ask for the exact set of N documents you > wnat from Solr in default order, re-order the resulting documents in the > magic order you already know and care about, and then give that modified > response to your front end. > > > -Hoss > http://www.lucidworks.com/ > -- Thanks & Regards, Apoorva
