msfroh opened a new pull request #2088:
URL: https://github.com/apache/lucene-solr/pull/2088


   FieldNumbers.clear() is called from IndexWriter.deleteAll(), which is
   supposed to completely reset the state of the index. This includes
   clearing all known fields.
   
   Prior to this change, it would allocate progressively higher field
   numbers, which results in larger and  larger arrays for
   FieldInfos.byNumber, effectively "leaking" field numbers every time
   deleteAll() is called.
   
   <!--
   _(If you are a project committer then you may remove some/all of the 
following template.)_
   
   Before creating a pull request, please file an issue in the ASF Jira system 
for Lucene or Solr:
   
   * https://issues.apache.org/jira/projects/LUCENE
   * https://issues.apache.org/jira/projects/SOLR
   
   You will need to create an account in Jira in order to create an issue.
   
   The title of the PR should reference the Jira issue number in the form:
   
   * LUCENE-####: <short description of problem or changes>
   * SOLR-####: <short description of problem or changes>
   
   LUCENE and SOLR must be fully capitalized. A short description helps people 
scanning pull requests for items they can work on.
   
   Properly referencing the issue in the title ensures that Jira is correctly 
updated with code review comments and commits. -->
   
   
   # Description
   
   If you run a loop that repeatedly adds documents to an IndexWriter and calls 
deleteAll, new fields will be given progressively higher index numbers. Since 
these index numbers are reflected in the size of the FieldInfos.byNumber array, 
this is effectively a memory leak.
   
   # Solution
   
   Reset lowestUnassignedFieldNumber to -1 when FieldNumbers.clear() is called 
(resetting the state to that of a newly-created FieldNumbers instance).
   
   # Tests
   
   Added a unit test to confirm that after calling clear(), the next field is 
given number 0.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms 
to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [x] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended)
   - [x] I have developed this patch against the `master` branch.
   - [x] I have run `./gradlew check`.
   - [x] I have added tests for my changes.
   - [ ] I have added documentation for the [Ref 
Guide](https://github.com/apache/lucene-solr/tree/master/solr/solr-ref-guide) 
(for Solr changes only).
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to