TieredMergePolicy and expungeDeletes behaviour
----------------------------------------------
Key: SOLR-2725
URL: https://issues.apache.org/jira/browse/SOLR-2725
Project: Solr
Issue Type: Bug
Affects Versions: 3.3
Reporter: Martijn van Groningen
Fix For: 3.4, 4.0
During executing a commit with expungeDeletes I noticed there were still a lot
of segments left.
My solconfig.xml (that uses TieredMergePolicy, b/c luceneMatchVersion=3.3)
contained:
{code:xml}
<indexDefaults>
<mergeFactor>5</mergeFactor>
{code}
However there were still ~30 segments left with deletes after the commit
finished.
After looking in SolrIndexConfig class I noticed that
TieredMergePolicy#setMaxMergeAtOnceExplicit and
TieredMergePolicy#setExpungeDeletesPctAllowed aren't invoked.
I think the following statements should be added to the
SolrIndexConfig#buildMergePolicy method:
{code}
tieredMergePolicy.setMaxMergeAtOnceExplicit(mergeFactor);
tieredMergePolicy.setExpungeDeletesPctAllowed(0);
{code}
I think these changes should reflect the behavior of Solr 3.1 / 3.2
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
