[
https://issues.apache.org/jira/browse/SOLR-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416107#comment-15416107
]
ASF GitHub Bot commented on SOLR-9055:
--------------------------------------
GitHub user hgadre opened a pull request:
https://github.com/apache/lucene-solr/pull/67
[SOLR-9055] Make collection backup/restore extensible
- Introduced a Strategy interface to define how the Solr index data is
backed up.
- Two concrete implementations of this strategy interface defined.
- One using core Admin API (BACKUPCORE)
- Other skipping the backup of index data altogether. This is useful when
the index data is copied via an external mechanism in combination with
named
snapshots (Please refer to SOLR-9038 for details)
- In future we can add additional implementations of this interface (e.g.
based on HDFS snapshots etc.)
- Added a backup property to record the Solr version. This helps to check
the compatibility
of backup with respect to the current version during the restore
operation. This
compatibility check is not added since its unclear what the Solr level
compatibility guidelines
are. But at-least having version information as part of the backup would
be very useful.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hgadre/lucene-solr SOLR-9055_fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/67.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #67
----
commit ee07e54a36989637c39b110f1cba19c8af14a0fb
Author: Hrishikesh Gadre <hga...@cloudera.com>
Date: 2016-08-10T21:41:12Z
[SOLR-9055] Make collection backup/restore extensible
- Introduced a Strategy interface to define how the Solr index data is
backed up.
- Two concrete implementations of this strategy interface defined.
- One using core Admin API (BACKUPCORE)
- Other skipping the backup of index data altogether. This is useful when
the index data is copied via an external mechanism in combination with
named
snapshots (Please refer to SOLR-9038 for details)
- In future we can add additional implementations of this interface (e.g.
based on HDFS snapshots etc.)
- Added a backup property to record the Solr version. This helps to check
the compatibility
of backup with respect to the current version during the restore
operation. This
compatibility check is not added since its unclear what the Solr level
compatibility guidelines
are. But at-least having version information as part of the backup would
be very useful.
----
> Make collection backup/restore extensible
> -----------------------------------------
>
> Key: SOLR-9055
> URL: https://issues.apache.org/jira/browse/SOLR-9055
> Project: Solr
> Issue Type: Task
> Reporter: Hrishikesh Gadre
> Assignee: Mark Miller
> Attachments: SOLR-9055.patch, SOLR-9055.patch, SOLR-9055.patch
>
>
> SOLR-5750 implemented backup/restore API for Solr. This JIRA is to track the
> code cleanup/refactoring. Specifically following improvements should be made,
> - Add Solr/Lucene version to check the compatibility between the backup
> version and the version of Solr on which it is being restored.
> - Add a backup implementation version to check the compatibility between the
> "restore" implementation and backup format.
> - Introduce a Strategy interface to define how the Solr index data is backed
> up (e.g. using file copy approach).
> - Introduce a Repository interface to define the file-system used to store
> the backup data. (currently works only with local file system but can be
> extended). This should be enhanced to introduce support for "registering"
> repositories (e.g. HDFS, S3 etc.)
--
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
