[
https://issues.apache.org/jira/browse/SOLR-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889169#comment-13889169
]
Shawn Heisey commented on SOLR-5688:
------------------------------------
I absolutely love the idea here. The implementation feels awkward, though.
I've written my fair share of awkward code, so I hope you'll find this to be
*constructive* criticism.
What I envision is something that works with a URL like the following, with the
name of the handler and the specific action parameter something that can be
hashed out together. Even this action name feels awkward, but I like the idea
of having a bunch of parameters instead of separate actions. It allows you to
make one API call to change all related parameters:
/solr/admin/transientconfig?action=UPDATEAUTOCOMMITPARAMS&autoCommitMaxTime=NNNN&autoCommitMaxDocs=NNNN&autoSoftCommitMaxTime=NNNN&autoSoftCommitMaxDocs=NNNN
> 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.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]
