lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jose Carlos Canova <>
Subject Re: make data search as index progress.
Date Mon, 14 Apr 2014 13:01:56 GMT

That's because NRTCachingDirectory uses a in cache memory to "mimic in
memory the Directory that you used to index your files ", in theory the
commit is needed because you need to flush the documents recently added
otherwise this document will not be available for search until the end of
the indexing when you really need to flush all documents to the index to
close properly the "task that you created to index the documents", you can
adopt other strategies for NRT, one alternative is work with several index
segments with a fixed document length (like at each X docs you commit the
index and close it) using a new instance of a CompositeReader to perform
the search, works at same manner, since the CompositeReader as the name
says open an IndexReader for a IndexSearcher using list of Indexes.

Will work at same manner but with the disadvantage is that you have to
create your own code.

On Mon, Apr 14, 2014 at 9:29 AM, Jason Wee <> wrote:

> Hello,
> We are using lucene 4.6.0 and storing index on top of cassandra.
> As far as I understand, in order to make the index searchable, in the
> IndexFiles, method commit() has to be called, is there any other way so
> that the index is searchable other than calling commit() ?
> Took a look on the NRTCachingDirectory,  but our search and index
> application exists in two separate jvm, as far as NRT is concern, instance
> of NRTCachingDirectory needed to pass in IndexWriter and DirectoryReader to
> make it searchable.
> Thanks and appreciate any advice.
> /Jason

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message