lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Humphrey (JIRA)" <>
Subject [jira] Commented: (LUCENE-2282) Expose IndexFileNames as public, and make use of its methods in the code
Date Tue, 23 Feb 2010 21:11:28 GMT


Marvin Humphrey commented on LUCENE-2282:

It seems to me that identifying only core index files conflicts with the idea
of pluggable index formats.  Presumably plugins would use their own file
extensions.  Would these belong to the index, according to a detector based
off of IndexFileNames?  Presumably not, which would either limit the
usefulness of such a utility, or outright encourage anti-patterns such as a
sweeper that zaps files created by plugins because they aren't "core Lucene"

Also, are temporary files "core Lucene"?  Lockfiles?  Only sometimes?

What are the applications that we are trying to support by exposing this API?

> 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
>             Fix For: 3.1
> 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