I am not sure I fully understood the desired transformation, but
perhaps something from https://people.apache.org/~hossman/rev2016/
would help.
I am specifically thinking of:
*) f.person.qf example
*) ${people} example
Regards,
Alex.
On 27 February 2018 at 15:20, simon wrote:
> We do quite c
Thanks Mikhail:
I considered that, but not all queries would request that field, and there
are in fact a couple more similar DocTransformer-generated aliased fields
which we can optionally request, so it's not a general enough solution.
-Simon
On Wed, Feb 28, 2018 at 1:18 AM, Mikhail Khludnev w
Hello, Simon.
You can define a search handler where have
numcites:[subquery]&numcites.fl=pmid&numcites.q={!terms
f=md_c_pmid
v=$row.pmid}&numcites.rows=10&numcites.logParamsList=q
or something like that.
On Tue, Feb 27, 2018 at 11:20 PM, simon wrote:
> We do quite complex data pulls from a So
r/guide/6_6/update-request-
> processors.html
>
> From: solr-user@lucene.apache.org At: 02/27/18 20:21:08To:
> solr-user@lucene.apache.org
> Subject: Defining Document Transformers in Solr Configuration
>
> We do quite complex data pulls from a Solr index for subsequent analy
We do quite complex data pulls from a Solr index for subsequent analytics,
currently using a home-grown Python API. Queries might include a handful
of pseudofields which this API rewrites to an aliased field invoking a
Document Transformer in the 'fl' parameter list.
For example 'numcites' is tra
