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 <hossman_luc...@fucit.org> wrote: > > : 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 mean by "not an issue" ... i would argue that if a > client asks for the first 10 matches, and you return a numFound of 678 but > only give back 8 matches (because you have "excluded" two from that first > page) that that's a bug. > > I think most people would agree that the "correct" way to exclude a > document would be to tie into the logic of executing the executing the > main query (like QEC does, or via a filter query) so that if a user asks > for the first 10 documents, you give them the first 10 documents - no > matter how many are being excluded. > > > -Hoss
