[ https://issues.apache.org/jira/browse/SOLR-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485888#comment-14485888 ]
Yonik Seeley commented on SOLR-7332: ------------------------------------ Yeah, recentUpdates should be fine... on startup, the other stuff like oldDeletes is populated via recentUpdates. > Seed version buckets with max version from index > ------------------------------------------------ > > Key: SOLR-7332 > URL: https://issues.apache.org/jira/browse/SOLR-7332 > Project: Solr > Issue Type: Sub-task > Components: SolrCloud > Reporter: Timothy Potter > Assignee: Timothy Potter > Attachments: SOLR-7332.patch, SOLR-7332.patch, SOLR-7332.patch, > SOLR-7332.patch > > > See full discussion with Yonik and I in SOLR-6816. > The TL;DR of that discussion is that we should initialize highest for each > version bucket to the MAX value of the {{__version__}} field in the index as > early as possible, such as after the first soft- or hard- commit. This will > ensure that bulk adds where the docs don't exist avoid an unnecessary lookup > for a non-existent document in the index. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org