FAQ
Allow configurable deletion policy
----------------------------------

Key: SOLR-617
URL: https://issues.apache.org/jira/browse/SOLR-617
Project: Solr
Issue Type: New Feature
Components: search, update
Affects Versions: 1.3
Reporter: Noble Paul
Priority: Minor


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
{code:xml|title=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>
{code}




--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 19 | next ›
Discussion Overview
groupsolr-dev @
categorieslucene
postedJul 7, '08 at 6:19a
activeSep 29, '08 at 3:39a
posts19
users1
websitelucene.apache.org...

1 user in discussion

Shalin Shekhar Mangar (JIRA): 19 posts

People

Translate

site design / logo © 2019 Grokbase