As far as I understand, the db initialization happens at the start of the crawl.
When the db is initialized, this is where the ensurePartitions happens. However, for each start of the crawl, we do not have the current crawl ID until after the crawl actually starts, so the previous crawl ID is the max ID.
As far as I understand, the db initialization happens at the start of the crawl.
When the db is initialized, this is where the ensurePartitions happens. However, for each start of the crawl, we do not have the current crawl ID until after the crawl actually starts, so the previous crawl ID is the max ID.