Thanks Marcus for your response.
Best,
Mark
On Wed, Feb 24, 2021 at 4:50 PM Markus Jelsma
wrote:
> I would stick to the query elevation component, it is pretty fast and
> easier to handle/configure elevation IDs, instead of using function queries
> for it. We have customers that set a dozen of
I would stick to the query elevation component, it is pretty fast and
easier to handle/configure elevation IDs, instead of using function queries
for it. We have customers that set a dozen of documents for a given query
and it works just fine.
I also do not expect the function query variant to be
Thanks for the reply Markus!
I did try it.
My question specifically was (repasting here):-
Which is more recommended/ performant?
Note:- Assume that I have hundreds of ids to boost like this.
Is there a difference to the answer if docs to be boosted after the sort is
less?
Thanks!
Mark
On Wed,
Hello,
You are probably looking for the elevator component, check it out:
https://lucene.apache.org/solr/guide/8_8/the-query-elevation-component.html
Regards,
Markus
Op wo 24 feb. 2021 om 11:59 schreef Mark Robinson :
> Hi,
>
> I wanted to sort and then boost some docs to the top and these docs
Hi,
I wanted to sort and then boost some docs to the top and these docs should
be my first set in the results and the following ones appearing according
to my sort criteria.
I understand that sort overrides bq hence bq may not be used in this case
- I brought my boost into sort using "query()" a
