[prev in list] [next in list] [prev in thread] [next in thread]
List: solr-dev
Subject: [jira] Updated: (SOLR-617) Allow configurable deletion policy
From: "Shalin Shekhar Mangar (JIRA)" <jira () apache ! org>
Date: 2008-09-26 21:17:44
Message-ID: 1010924941.1222463864429.JavaMail.jira () brutus
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/SOLR-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Shalin Shekhar Mangar updated SOLR-617:
---------------------------------------
Attachment: solr-617.patch
Updated with more javadocs and comments in solrconfig.xml
I think this is ready to go in. I'll commit this in a day or two if there are no \
objection.
> 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.4
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 1.4
>
> Attachments: 617.patch, solr-617.patch, solr-617.patch, solr-617.patch, \
> solr-617.patch, solr-617.patch
>
> 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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic