You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Rafał Kuć (JIRA)" <ji...@apache.org> on 2014/02/02 22:22:08 UTC

[jira] [Updated] (SOLR-5688) Allow updating of soft and hard commit parameters using HTTP API

     [ https://issues.apache.org/jira/browse/SOLR-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafał Kuć updated SOLR-5688:
----------------------------

    Attachment: SOLR-5688.patch

Attaching a draft patch adding new request handler which allows changing autocommit values - comments welcome :) 

I made it working on the core level. If everyone find it useful, collections API can be extended to allow such operation for the whole collection.

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org