I am not disputing that, the most general way to do it is to exclude hits just
like you said.
Was just thinking aloud about my particular use case, where I do not care about
pagination.
Thanks for your comments,
e.
On Oct 29, 2012, at 10:58 PM, Chris Hostetter wrote:
>
> : I did not look
: I did not look where pagination happens, but it looks like
: DocTransform gets applied at the very end (response writer), which in
: turn means pagination is not an issue , just soma pages might get
: shorter due to this additional filtering, but that is quite ok for me.
it depends on what you
Thanks Hoss,
I probably did not formulate the question properly, but you gave me an answer.
I do it already in SearchComponent, just wanted to centralise this
control of the depth and width of the response to the single place in
code [style={minimal, verbose, full...}].
It just sounds logical t
: Transformer is great to augment Documents before shipping to response,
: but what would be a way to prevent document from being delivered?
DocTransformers can only modify the documents -- not hte Document List.
what you are describing would have to be done as a SearchComponent (or in
the QPar
Transformer is great to augment Documents before shipping to response,
but what would be a way to prevent document from being delivered?
I have some search components that make some conclusions after search
, duplicates removal, clustering and one Augmenter(solr Transformer)
to shape the response
