lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] Commented: (LUCENE-2282) Expose IndexFileNames as public, and make use of its methods in the code
Date Wed, 24 Feb 2010 17:00:27 GMT


Shai Erera commented on LUCENE-2282:

bq. But I don't think we should back port to 3.0.2

Ok, I can live w/ 3.1, as long as it's not released at the end of 2010. I can for now put
that part of my code in o.a.l.index, until 3.1 is out.

As I wrote in the TestFileSwitchDirectory comment, this IMO has to go in, because otherwise
it would make the code of users of FSD fragile (potentially).

Thanks for looking at this !

> Expose IndexFileNames as public, and make use of its methods in the code
> ------------------------------------------------------------------------
>                 Key: LUCENE-2282
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Shai Erera
>            Assignee: Michael McCandless
>             Fix For: 3.1
>         Attachments: LUCENE-2282.patch, LUCENE-2282.patch, LUCENE-2282.patch
> IndexFileNames is useful for applications that extend Lucene, an in particular those
who extend Directory or IndexWriter. It provides useful constants and methods to query whether
a certain file is a core Lucene file or not. In addition, IndexFileNames should be used by
Lucene's code to generate segment file names, or query whether a certain file matches a certain
> I'll post the patch shortly.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message