[ 
https://issues.apache.org/jira/browse/SOLR-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340021#comment-15340021
 ] 

Varun Thacker commented on SOLR-7374:
-------------------------------------

Hi Hrishikesh,

 bq. So in case there are multiple repositories configured, we need a way to 
configure which repository to use

Alternatively how do you feel about forcing a default repository if multiple 
repos are configured? Currently if there is just 1 we make that default but 
when there are multiple repositories we don't necessarily need to provide a 
default.

Mark - Sure I can assign it to myself. I'd like your opinion and Hrishikesh's 
opinion on this comment though  -

{code}
I had to implement this test as a "cloud" test so as to enable testing these 
core level operations (since these operations are enabled only in the cloud 
mode). The collection-level changes include,
- Backup/restore collection metadata
- Check the version compatibility during restore
- Strategy interface to define "how" backup operation is performed (e.g. 
copying the index files vs. a file-system snapshot etc.)
{code}

I feel the first point should be part of this Jira . We can then say this patch 
effectively solves makes the repository interface work for both standalone and 
cloud.

Points 2/3 seem more like better guarantee checks and more options and aren't 
cloud related. We could tackle that in SOLR-9055

> Backup/Restore should provide a param for specifying the directory 
> implementation it should use
> -----------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7374
>                 URL: https://issues.apache.org/jira/browse/SOLR-7374
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Varun Thacker
>            Assignee: Mark Miller
>             Fix For: 6.2
>
>         Attachments: SOLR-7374.patch, SOLR-7374.patch, SOLR-7374.patch, 
> SOLR-7374.patch, SOLR-7374.patch, SOLR-7374.patch, SOLR-7374.patch
>
>
> Currently when we create a backup we use SimpleFSDirectory to write the 
> backup indexes. Similarly during a restore we open the index using 
> FSDirectory.open . 
> We should provide a param called {{directoryImpl}} or {{type}} which will be 
> used to specify the Directory implementation to backup the index. 
> Likewise during a restore you would need to specify the directory impl which 
> was used during backup so that the index can be opened correctly.
> This param will address the problem that currently if a user is running Solr 
> on HDFS there is no way to use the backup/restore functionality as the 
> directory is hardcoded.
> With this one could be running Solr on a local FS but backup the index on 
> HDFS etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to