lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jyothsna Bavisetti <>
Subject need suggetion in replacing forcemerge(1) with alternative which consumes less space
Date Tue, 14 Apr 2020 05:52:20 GMT
HI Team,


1.We Upgraded Lucene 4.6 to 8+, After upgrading we are facing issue with Lucene Index Creation.

We are indexing in Multi-threading environment. When we create bulk indexes , Lucene Document
is getting corrupted. (data is not getting updated correctly. Merging of different row data).

2. when we are trying to updateDocument method for single record. It is not reflecting in
IndexReader until the count is 8.  Once the count exceeds, than records are visible for IndexReader.
(creating 8 segment files.) is there any alternative for reducing these segment file creation.

3. above two issues are resolved by forcemerge(1). But it is not feasible for our use case
, because it takes 3X memory. We are creating indexes for huge data.


Please suggest some ideas alternate of forceMerge, dealing with indexwriter.commit for multithreading,
committing  data while updating single record.






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