[
https://issues.apache.org/jira/browse/SOLR-16461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625839#comment-17625839
]
Sanjay Dutt commented on SOLR-16461:
------------------------------------
In v1 version, initial configuration is passed through the `solrconfig.xml`.
{{}}
{code:java}
<requestHandler name="/replication" class="solr.ReplicationHandler">
<lst name="leader"> <str name="replicateAfter">optimize</str>
<str name="backupAfter">optimize</str>
<str name="confFiles">schema.xml,stopwords.txt,elevate.xml</str> </lst>
<int name="maxNumberOfBackups">2</int> <str
name="commitReserveDuration">00:00:10</str>
<lst name="invariants"> <str name="maxWriteMBPerSec">16</str>
</lst>
</requestHandler>{code}
{{}}
In JAS-RX v2 case, we do not have such type of configuration in place in which
API's can be configured to start with some parameters.
Now We are looking into this. How we can use that configuration?
But that also brings up the new question which is that IF we are actually
moving away from the handlers. Do we really need to use the same old
configuration or we need to come up with some new way of adding those
parameters to v2 APIs?
> Create v2 equivalent of v1 ReplicationHandler 'BACKUP'
> ------------------------------------------------------
>
> Key: SOLR-16461
> URL: https://issues.apache.org/jira/browse/SOLR-16461
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Affects Versions: 9.1
> Reporter: Sanjay Dutt
> Priority: Major
> Labels: V2
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> A backup API for user manager cluster or single node installation has no v2
> equivalent. This ticket is used to track changes that will be made to add the
> v2 API for the 'backup'.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
