lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Closed] (SOLR-3476) Create a Solr Core with a given commit point
Date Fri, 14 Oct 2016 11:18:20 GMT


Jan Høydahl closed SOLR-3476.
    Resolution: Won't Fix

Closing as won't fix.
If you want to stage content for controlled publishing at a certain time, please create a
separate SolrCloud collection, and then flip aliases to set into production.

> Create a Solr Core with a given commit point
> --------------------------------------------
>                 Key: SOLR-3476
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: multicore
>    Affects Versions: 3.6
>            Reporter: Ludovic Boutros
>              Labels: patch
>         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 was sent by Atlassian JIRA

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

View raw message