Skip to content
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

Closed
wants to merge 6 commits into from
Closed

Upgrade to Lucene r1660560 #9746

wants to merge 6 commits into from

Conversation

rmuir
Copy link
Contributor

@rmuir rmuir commented Feb 18, 2015

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.

  1. TODO: needsScores: we aren't properly taking advantage of this, and something might not be right here
  2. TODO: topdocs.merge, we are stricter and some loose stuff is happening.
  3. Generate @OVERRIDES for any overriden methods. This is a very useful tool when dealing with API changes/refactoring. It is crazy not to use it.
  4. remove deprecated use of TermFilter
  5. review "take 1" commits, we found a few unrelated bugs (e.g. assuming DIS.iterator() could not be null and other silly stuff)

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.

@rjernst
Copy link
Member

rjernst commented Feb 18, 2015

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...
Copy link
Contributor

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).

@rmuir
Copy link
Contributor Author

rmuir commented Feb 18, 2015

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...

@jpountz
Copy link
Contributor

jpountz commented Feb 18, 2015

I'm looking into those TopDocs.merge issues.

@jpountz
Copy link
Contributor

jpountz commented Feb 18, 2015

@mikemccand I pushed a new commit that hopefully makes usage of TopDocs.merge better. Let me know what you think?

@mikemccand
Copy link
Contributor

Thanks @jpountz that looks much cleaner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >upgrade v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants