I think it can, but it's sort of tricky thing to implement.

On Tue, Jan 27, 2015 at 10:29 PM, Alexandre Rafalovitch <arafa...@gmail.com>
wrote:

> Can this be done as a custom post-filter with the recent Solr improvements?
>
> Regards,
>    Alex.
> ----
> Sign up for my Solr resources newsletter at http://www.solr-start.com/
>
>
> On 27 January 2015 at 14:22, Mikhail Khludnev
> <mkhlud...@griddynamics.com> wrote:
> > Hello,
> > if I get you right it's frequently requested feature, but it requires
> > really deep hack like
> > https://issues.apache.org/jira/browse/LUCENE-6066
> >
> >
> >
> > On Tue, Jan 27, 2015 at 9:28 PM, Jorge Luis Betancourt González <
> > jlbetanco...@uci.cu> wrote:
> >
> >> Hi all,
> >>
> >> Recently I got an interesting use case that I'm not sure how to
> implement,
> >> the idea is that the client wants a fixed number of documents, let's
> call
> >> it N, to appear in the top of the results. Let me explain a little we're
> >> working with web documents so the idea is too promote the documents that
> >> match the query of the user from a given domain (wikipedia, for
> example) to
> >> the top of the list. So if I apply a a boost using the boost parameter:
> >>
> >>
> >>
> http://localhost:8983/solr/select?q=search&fl=url&boost=map(query($type1query),0,0,1,50)&type1query=host:wikipedia
> >>
> >> I get *all* the documents from the desired host at the top, but there is
> >> no way of limiting the number of documents from the host that are
> boosted
> >> to the top of the result list (which could lead to several pages of
> content
> >> from the same host, which is not desired, the idea is to only show N) .
> I
> >> was thinking in something like field collapsing/grouping but only for
> the
> >> documents that match my $type1query parameter (host:wikipedia) but I
> don't
> >> see any way of doing grouping/collapsing on only one group and leave the
> >> other results untouched.
> >>
> >> I although thought on using 2 groups using group.query=host:wikipedia
> and
> >> group.query=-host:wikipedia, but in this case there is no way of
> >> controlling how much documents each independently group will have.
> >>
> >> In this particular case QueryElevationComponent it's not helping
> because I
> >> don't want to map all the posible queries I just want to put the some of
> >> the results from a certain host in the top of the list, but without
> >> boosting all the documents from the same host.
> >>
> >> Any thoughts or recommendations on this?
> >>
> >> Thank you,
> >>
> >> Regards,
> >>
> >>
> >> ---------------------------------------------------
> >> XII Aniversario de la creación de la Universidad de las Ciencias
> >> Informáticas. 12 años de historia junto a Fidel. 12 de diciembre de
> 2014.
> >>
> >>
> >
> >
> > --
> > Sincerely yours
> > Mikhail Khludnev
> > Principal Engineer,
> > Grid Dynamics
> >
> > <http://www.griddynamics.com>
> > <mkhlud...@griddynamics.com>
>



-- 
Sincerely yours
Mikhail Khludnev
Principal Engineer,
Grid Dynamics

<http://www.griddynamics.com>
<mkhlud...@griddynamics.com>

Reply via email to