[SOLR-617] Allow configurable deletion policy

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4
• Fix Version/s: 1.4
• Component/s: search, update
• Assignee: Shalin Shekhar Mangar
• Reporter: Noble Paul
• Created: 07/Jul/08 06:18
• Updated: 02/May/13 02:29
• Resolved: 29/Sep/08 03:38

Description

Lucene API provides means to configure deletion policy. Solr should be able to expose it through configuration in solrconfig.xml. Moreover the new replication (SOLR-561) strategy is going to rely on this .

I propose the configuration go into the <mainIndex> section

sample configuration

solrconfig.xml

<mainIndex>
    <!-- configure deletion policy here-->
    <deletionPolicy>
       <!-- Store only the commits with optimize.Non optimized commits will get deleted by lucene when 
               the last IndexWriter/IndexReader using this commit point is closed  -->
        <keepOptimizedOnly>true</keepOptimizedOnly>
         <!--Maximum no: of commit points stored . Older ones will be cleaned when they go out of scope-->
        <maxCommitsToKeep></maxCommitsToKeep>
         <!-- max age of a stored commit-->
        <maxCommitAge></maxCommitAge>    
    </deletionPolicy>
    
  </mainIndex>

Issue Links

• is depended upon by: SOLR-561 Solr replication by Solr (for windows also)