It looks like everything works fine without my custom component, which is good for Solr, bad for me. The custom component does some additional authorization processing to remove docs that the user does not have access to. To do this we're iterating through responseBuilder.getResults().docList and removing any documents that the user should not be able to see. Removing bad items works fine, but sorting isn't quite right after doing this. At this point is the docList completely sorted, or is there an optimization inside solr which only sorts the top X documents? I'm grabbing at straws here because for the life of me I can't figure out what is causing this.
I'm doing all of the filtering inside of the process method in my custom SearchComponent. On Fri, Feb 10, 2012 at 12:41 PM, Jamie Johnson <jej2...@gmail.com> wrote: > This is an snapshot of the solrcloud branch from somewhere between a > year and 6 months ago (can't really remember off hand) with some > custom components, I'm thinking that the custom components may be > messing something up. I'm removing them now to test this without > those to make sure that the issue is on my end, will report shortly. > > On Fri, Feb 10, 2012 at 12:16 PM, Yonik Seeley > <yo...@lucidimagination.com> wrote: >> On Fri, Feb 10, 2012 at 11:44 AM, Jamie Johnson <jej2...@gmail.com> wrote: >>> Was there a fix recently to address sorting issues for Dates in solr >>> cloud? On my cluster I have a date field which when I sort across the >>> cluster I get incorrect order executing the following query I get >> >> Yikes! There haven't been any fixes recently that I know of. >> What version of Solr is this? >> >> -Yonik >> lucidimagination.com
