lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ludovic Boutros (JIRA)" <>
Subject [jira] [Updated] (SOLR-3476) Create a Solr Core with a given commit point
Date Tue, 22 May 2012 15:50:41 GMT


ludovic Boutros updated SOLR-3476:

    Attachment: commitPoint.patch

This patch adds this functionality:

The STATUS command in the CoreAdminHandler gives now the generation of a core and the generation
list available in the index currently.
The core creation has now an additional parameter (optional): commitPointGeneration.
It is the generation of the wanted commit point.

I will add some more examples tomorrow.

If someone could check that everything is ok with this patch that would be great !

> Create a Solr Core with a given commit point
> --------------------------------------------
>                 Key: SOLR-3476
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: multicore
>    Affects Versions: 3.6
>            Reporter: ludovic Boutros
>         Attachments: commitPoint.patch
> In some configurations, we need to open new cores with a given commit point.
> For instance, when the publication of new documents must be controlled (legal obligations)
in a master-slave configuration there are two cores on the same instanceDir and dataDir which
are using two "versions" of the index.
> The switch of the two cores is done manually.
> The problem is that when the replication is done one day before the switch, if any problem
occurs, and we need to restart tomcat, the new documents are published.
> With this functionality, we could ensure that the index generation used by the core used
for querying is always the good one. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message