[
https://issues.apache.org/jira/browse/SOLR-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905800#comment-13905800
]
Steve Rowe commented on SOLR-5688:
----------------------------------
Rafał, I haven't looked at your code yet, I'll take a look some time later this
week.
Since we'll almost certainly have a persistent version of this as part of
SOLR-5200, I'm a little concerned about mixing transient and persistent changes
like this. And what if a distributed/SolrCloud node goes down and then comes
back up? Differing configurations might trigger weird conditions.
An alternative for some changes could be to always persist changes, but not
require core reloads?
> Allow updating of soft and hard commit parameters using HTTP API
> ----------------------------------------------------------------
>
> Key: SOLR-5688
> URL: https://issues.apache.org/jira/browse/SOLR-5688
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.6.1
> Reporter: Rafał Kuć
> Fix For: 5.0
>
> Attachments: SOLR-5688-single_api_call.patch, SOLR-5688.patch
>
>
> Right now, to update the values (max time and max docs) for hard and soft
> autocommits one has to alter the configuration and reload the core. I think
> it may be nice, to expose an API to do that in a way, that the configuration
> is not updated, so the change is not persistent.
> There may be various reasons for doing that - for example one may know that
> the application will send large amount of data and want to prepare for that.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
