David and Adrien, thanks for your responses. Bringing up an old thread here. Revisiting this question ... > (so deleted docs == max docs) and call commit. Will/Can this segment still > exist after commit?
SInce I am using Solr (8.11.1), the default deletion policy is SolrDeletionPolicy which retains only the latest commit by default and deletes the rest. In that case, would a segment be automatically deleted once all of the docs in it have been marked deleted (eg: via reindexing)? If yes, at what point (commit or merge)? Thanks, Rahul On Fri, Sep 23, 2022 at 9:25 AM Adrien Grand <jpou...@gmail.com> wrote: > On the 2nd question, we do not plan on leveraging this information to > figure out the codec: the codec that should be used to read a segment is > stored separately (also in segment infos). > > It is mostly useful for diagnostics purposes. E.g. if we see an interesting > corruption case where checksums match, we can guess that there is a bug > somewhere in Lucene in a version that is between this minimum version and > the version that was used to write the segment. > > On Sat, Sep 17, 2022 at 11:07 AM Dawid Weiss <dawid.we...@gmail.com> > wrote: > > > > (so deleted docs == max docs) and call commit. Will/Can this segment > > still > > > exist after commit? > > > > > > > Depends on your merge policy index deletion policy. You can configure > > Lucene to keep older commits (and then you'll preserve all historical > > segments). > > > > I don't know the answer to your second question. > > > > D. > > > > > -- > Adrien >
