lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: applyAllDeletes, writeAllDeletes
Date Sun, 28 May 2017 16:26:14 GMT
Sorry, yes, that commit was one of many on a feature branch I used to work
on LUCENE-5438, which added near-real-time index replication to Lucene.
Before this change, Lucene's replication module required a commit in order
to replicate, which is a heavy operation.

The writeAllDeletes boolean option asks Lucene to move all recent deletes
(tombstone bitsets) to disk while opening the NRT (near-real-time) reader.

Normally Lucene won't always do that, and will instead carry the bitsets in
memory from writer to reader, for reduced refresh latency.

What sort of custom changes do you have in this part of Lucene?

Mike McCandless

On Sat, May 27, 2017 at 10:35 PM, Nawab Zada Asad Iqbal <>

> Hi all
> I am looking at following change in lucene-solr which doen't mention any
> JIRA. How can I know more about it?
> "1ae7291 Mike McCandless on 1/24/16 at 3:17 PM current patch"
> Specifically, I am interested in what 'writeAllDeletes'  does in the
> following method. Let me know if it is very stupid question and I should
> have done something else before emailing here.
> static DirectoryReader open(IndexWriter writer, SegmentInfos infos,
> boolean applyAllDeletes, boolean writeAllDeletes) throws IOException {
> Background: We are running solr4.5 and upgrading to 6.5.1. We have
> some custom code in this area, which we need to merge.
> Thanks
> Nawab

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