lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6813) OfflineSorter.sort shouldn't remove the output Path up front
Date Thu, 24 Sep 2015 21:49:04 GMT


ASF subversion and git services commented on LUCENE-6813:

Commit 1705168 from [~mikemccand] in branch 'dev/branches/branch_5x'
[ ]

LUCENE-6813: OfflineSorter no longer removes its output file up front; fix file handle leak
in RangeTreeWriter

> OfflineSorter.sort shouldn't remove the output Path up front
> ------------------------------------------------------------
>                 Key: LUCENE-6813
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: Trunk, 5.4
>         Attachments: LUCENE-6813.patch, LUCENE-6813.patch, LUCENE-6813.patch
> The new BKD tree classes, and NumericRangeTree (just a 1D BKD tree),
> make heavy use of OfflineSorter to build their data structures at
> indexing time when the number of indexed documents is biggish.
> But when I was first building them (LUCENE-6477), I hit a thread
> safety issue in OfflineSorter, and at that time I just worked around
> it by creating my own private temp directory each time I need to write
> a BKD tree.
> This workaround is sort of messy, and it causes problems with "pending
> delete" files on Windows when we try to remove that temp directory,
> causing test failures like
> I think instead we should fix the root cause ... i.e. make
> OfflineSorter thread safe.  It looks like it's simple...
> Separately I'd like to somehow fix these BKD tests to catch any leaked
> file handles ... I'm not sure they are today.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message