[
https://issues.apache.org/jira/browse/SOLR-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348809#comment-15348809
]
Hrishikesh Gadre commented on SOLR-9242:
----------------------------------------
[~varunthacker] Thanks for the review.
bq. But now that its out and documented I don't think we can drop it easily.
Seems like a good way to override location anyways? We'll need to add support
for it now
Since we allow users to configure multiple repositories in solr.xml, we can not
use the current cluster property as is. This is because user may want to
specify different location for different file-systems (or repositories). Hence
at minimum we need one cluster property per repository configuration (e.g. name
could be <repository-name>-location).
For 6.x releases, we can restrict the users to configure only a *single*
repository at-a-time. This will avoid the problem mentioned above and they can
use the current property.
For 7.x releases, we have multiple options,
- Support configuring multiple cluster properties one per repository
configuration. This will require some changes in CLUSTERPROP API since
currently it requires fixed (or well-known) property names. In this case we
will remove the current cluster property as well as ability to configure
*default* location via solr.xml
- Continue using the current mechanism of configuring *default* location via
solr.xml. Just remove the current cluster property
What do you think?
> Collection level backup/restore should provide a param for specifying the
> repository implementation it should use
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-9242
> URL: https://issues.apache.org/jira/browse/SOLR-9242
> Project: Solr
> Issue Type: Improvement
> Reporter: Hrishikesh Gadre
> Assignee: Varun Thacker
> Attachments: SOLR-9242.patch
>
>
> SOLR-7374 provides BackupRepository interface to enable storing Solr index
> data to a configured file-system (e.g. HDFS, local file-system etc.). This
> JIRA is to track the work required to extend this functionality at the
> collection level.
--
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
