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 to me to have this possibility in
DocTransformer, as null document is kind of "extremely" modified
document.
Even better, it might actually work… (did not try it yet)
@Override
setContext( TransformContext context ) {
context.iterator = new FilteringIterator(context.iterator)
}
Simply by providing my own FilteringIterator that would skip document
I do not need in the response? Does this sound right from the
"legitimate api usage" perspective.
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.
On Mon, Oct 29, 2012 at 7:59 PM, Chris Hostetter
<hossman_luc...@fucit.org> wrote:
>
> : 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 QParser) -- take a look at QueryElevation component for an example of
> how to do something like this that plays nicely with pagination.
>
>
> -Hoss
