On Mon, Nov 9, 2009 at 7:53 PM, Daniel Noll wrote:
> On Tue, Nov 10, 2009 at 00:44, Michael McCandless
> wrote:
>> Stepping back, since presumably your app knows what it's storing in
>> the directory, can't you filter for files you know you've created?
>> What's the larger use case here?
>
> The
On Tue, Nov 10, 2009 at 00:44, Michael McCandless
wrote:
> Stepping back, since presumably your app knows what it's storing in
> the directory, can't you filter for files you know you've created?
> What's the larger use case here?
The exact use case where we were using list() is to determine whet
On Sun, Nov 8, 2009 at 4:58 PM, Daniel Noll wrote:
>> Well... you can use oal.index.IndexFileNameFilter.getFilter() to
>> filter for only the Lucene index files, or, you could filter for the
>> additional files you know you've placed in the index directory?
>
> This is the workaround we're curren
On Fri, Nov 6, 2009 at 20:26, Michael McCandless
wrote:
> Well... you can use oal.index.IndexFileNameFilter.getFilter() to
> filter for only the Lucene index files, or, you could filter for the
> additional files you know you've placed in the index directory?
This is the workaround we're currentl
Well... you can use oal.index.IndexFileNameFilter.getFilter() to
filter for only the Lucene index files, or, you could filter for the
additional files you know you've placed in the index directory?
The motivation for this change was that Directory is the wrong place
to have "smarts" about what is