Hence the suggestion to group by the paid field - would give you two lists of the number you ask for.
What I'm trying to say is that the QueryElevationComponent might do it, but it is also relatively clunky, so a pure search solution might do it. However, the thing we lack right now is a full take on the requirements, e.g. how should paid results be sorted, how many paid results do you show, etc, etc. Without these details we're all guessing. Upayavira On Thu, Oct 8, 2015, at 04:45 PM, Walter Underwood wrote: > Sorting all paid above all unpaid will give bad results when there are > many matches. It will show 1000 paid items, include all the barely > relevant ones, before it shows the first highly relevant unpaid recipe. > What if that was the only correct result? > > Two approaches that work: > > 1. Boost paid items using the “boost” parameter in edismax. Adjust it to > be a tiebreaker between documents with similar score. > > 2. Show two lists, one with the five most relevant paid, the next with > the five most relevant unpaid. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > > > On Oct 8, 2015, at 7:39 AM, Alessandro Benedetti > > <benedetti.ale...@gmail.com> wrote: > > > > Is it possible to understand better this : "as it doesn't > > allow any meaningful customization " ? > > > > Cheers > > > > On 8 October 2015 at 15:27, Andrea Roggerone <andrearoggerone.o...@gmail.com > >> wrote: > > > >> Hi guys, > >> I don't think that sorting is a good solution in this case as it doesn't > >> allow any meaningful customization.I believe that the advised > >> QueryElevationComponent is one of the viable alternative. Another one would > >> be to boost at query time a particular field, like for instance paid. That > >> would allow you to assign different boosts to different values using a > >> function. > >> > >> On Thu, Oct 8, 2015 at 1:48 PM, Upayavira <u...@odoko.co.uk> wrote: > >> > >>> Or just have a field in your index - > >>> > >>> paid: true/false > >>> > >>> Then sort=paid desc, score desc > >>> > >>> (you may need to sort paid asc, not sure which way a boolean would sort) > >>> > >>> Question is whether you want to show ALL paid posts, or just a set of > >>> them. For the latter you could use result grouping on the paid field. > >>> > >>> Upayavira > >>> > >>> On Thu, Oct 8, 2015, at 01:34 PM, NutchDev wrote: > >>>> Hi Christian, > >>>> > >>>> You can take a look at Solr's QueryElevationComponent > >>>> <https://wiki.apache.org/solr/QueryElevationComponent> . > >>>> > >>>> It will allow you to configure the top results for a given query > >>>> regardless > >>>> of the normal lucene scoring. Also you can specify exclude document > >> list > >>>> to > >>>> exclude certain results for perticular query. > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> View this message in context: > >>>> > >>> > >> http://lucene.472066.n3.nabble.com/How-to-show-some-documents-ahead-of-others-tp4233481p4233490.html > >>>> Sent from the Solr - User mailing list archive at Nabble.com. > >>> > >> > > > > > > > > -- > > -------------------------- > > > > Benedetti Alessandro > > Visiting card - http://about.me/alessandro_benedetti > > Blog - http://alexbenedetti.blogspot.co.uk > > > > "Tyger, tyger burning bright > > In the forests of the night, > > What immortal hand or eye > > Could frame thy fearful symmetry?" > > > > William Blake - Songs of Experience -1794 England >
