vigyasharma commented on issue #14362:
URL: https://github.com/apache/lucene/issues/14362#issuecomment-2756963298
Sounds good to me. Will watch out for your PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
guojialiang92 commented on issue #14362:
URL: https://github.com/apache/lucene/issues/14362#issuecomment-2753129754
Thanks @vigyasharma. Your understanding is correct (**This is specifically a
problem for segment replication**).
From an implementation point of view, similar to the cu
vigyasharma commented on issue #14362:
URL: https://github.com/apache/lucene/issues/14362#issuecomment-2752804917
Thanks @guojialiang92 . Is the plan here to support creating an IndexWriter
with a supplied value of `counter`, say `N`, so that all it's commit
generations are `>=N` i.e. `segm
guojialiang92 commented on issue #14362:
URL: https://github.com/apache/lucene/issues/14362#issuecomment-2747968162
Hi @vigyasharma
I will explain the usage scenarios.
In the **segment replication** scenario, the file name and content of the
replica and the primary shard will be c
vigyasharma commented on issue #14362:
URL: https://github.com/apache/lucene/issues/14362#issuecomment-2731919938
Hi @guojialiang92, Could you elaborate more on how you plan to use this
capability? It's not immediately obvious why modifying `segmentInfos.counter`
will help with peer recover
guojialiang92 opened a new issue, #14362:
URL: https://github.com/apache/lucene/issues/14362
### Description
Can we support modifying `segmentInfos.counter` in `IndexWriter`?
This can be used to skip some segment names when writing.
In the scenario of enabling `segment replicatio
