[
https://issues.apache.org/jira/browse/SOLR-16852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741762#comment-17741762
]
David Smiley commented on SOLR-16852:
-------------------------------------
Wouldn't commit metadata be a more general way to track a queue offset (or
similar)? This seems like information that isn't truly backup-oriented, it
seems index-oriented, and thus could be used even if backups aren't involved.
I suppose a challenge might be sharding, since not all shards are updated by
recent indexing. Nonetheless I could imagine a new mechanism to fetch the most
recent commit metadata.
> Let backups have custom key/values
> ----------------------------------
>
> Key: SOLR-16852
> URL: https://issues.apache.org/jira/browse/SOLR-16852
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomas Eduardo Fernandez Lobbe
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently backups have some properties attached such as configName,
> collectionAlias, indexVersion, etc. It would be useful to allow custom
> properties/annotations to add some information coming from the process that
> triggers the backup. For example, say you have a process that consumes from a
> queue, adds documents to Solr and then triggers a backup command, the backup
> could include the queue offset at the time of triggering the backup so that
> the application could potentially continue processing from such offset upon
> restore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
