New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Lucene r1660560 #9746
Conversation
parts that fail because of bad assumptions
FYI, I re-enabled the non debuggable test (indeed it was very difficult to debug) and commented out the portions that cause problems, along with adding comments as to why they fail. |
TopFieldDocs[] shardDocs = new TopFieldDocs[aggregations.size()]; | ||
for (int i = 0; i < shardDocs.length; i++) { | ||
InternalTopHits topHitsAgg = (InternalTopHits) aggregations.get(i); | ||
// TODO: topdocs.merge is this really safe? our topDocs is a TopFieldDocs... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jpountz could you have a look at this one? It made me nervous (not sure the stronger typing is safe).
whew, awesome ryan! Thanks for all your help here (mike too). Another thing to mention, the "TODO: topdocs.merge" (there are two of these), we need to look into them. Mike had them as nocommits and maybe they should be... |
I'm looking into those TopDocs.merge issues. |
@mikemccand I pushed a new commit that hopefully makes usage of TopDocs.merge better. Let me know what you think? |
Thanks @jpountz that looks much cleaner. |
This isnt an easy one. I deferred a lot of work until later.
There are a lot of followups we can do. I don't plan on working on these, or opening issues for these, they are just ideas.
One test is especially bad. It is not debuggable and I disabled it. It tries to use the postings lists (in wierd ways) from groovy apis or something like that. Besides the point of testing, this alone seems like a bad idea. We should remove tests like this from the codebase, they just waste time. This test really ruined my day and discouraged me from working any further. Please consider the person debugging when writing tests.