incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Hunt <>
Subject Re: question on default block caching file exclusions
Date Sat, 13 Oct 2012 00:05:15 GMT
Re the "code cleanup" comment. What are your thoughts on removing the
metablock code in favor of using Lucene's new (4.0) AppendingCodec?
Alternately it could be made optional controlled by user configuration
(ie switch file writers).


On Fri, Oct 12, 2012 at 4:15 PM, Aaron McCurry <> wrote:
> FYI, I'm planning on cleaning up the code this weekend and move the
> projects to Lucene 4.0 and begin the transition to the new Thrift RPC
> API.
> Aaron
> On Fri, Oct 12, 2012 at 6:53 PM, Aaron McCurry <> wrote:
>> So if you are looking the new-api-project you are correct.  In the
>> master take a look at
>> o.a.b.manager.indexserver.DistributedIndexServer:501.  Unfortunately
>> the project is spread between 2 versions of Lucene and that's why
>> there's no reference in the new api branch code.  Does this help?
>> Aaron
>> On Fri, Oct 12, 2012 at 6:34 PM, Patrick Hunt <> wrote:
>>> Hi, I noticed this comment on the wiki:
>>> "To control the blockCachingFileTypes create a set with the given
>>> Lucene file type extensions that you wish to cache. If you leave this
>>> null the default is to cache ALL Lucene file types except for the FDT
>>> and FDX file types which are used for data retrieval only and are not
>>> accessed during the search itself."
>>> However I don't see in the code where this default is set. afaict all
>>> file types are cached in the default case. What am I missing?
>>> Patrick

View raw message