Resolved: (LUCENE-623) RAMDirectory.close() should have acomment about not releasing any r
0 answers - 1134 bytes -
[ ] Hoss Man resolved LUCENE-623: Resolution: Fixed Patch commited. Note that this patch caused an NPE in , but after reviewing the test I'm of the opinion that it made an invalid assumption about the order of events that was allowed, to the effect of Directory merged = new RAMDirectory(); merged.close(); IndexReader reader = IndexReader.open(merged); I modified the test slightly to only close the directory once all uses of it were finished and included it in the commit. RAMDirectory.close() should have a comment about not releasing any resources Key: LUCENE-623 URL: Project: Lucene - Java Type: Improvement Components: Store Versions: 1.9 Reporter: Heng Mei Assignee: Hoss Man Priority: Minor Attachments: ramdirectory.diff I wrongly assumed that calling RAMDirectory.close() would free up the memory occupied by the RAMDirectory. It might be helpful to add a javadoc comment that warns users that RAMDirectory.close() is a no-op, since it might be a common assumption that close() would release resources.
Re: Resolved: (LUCENE-623) RAMDirectory.close() should have acomment about not releasing any r