[
https://issues.apache.org/jira/browse/SOLR-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777326#action_12777326
]
Hoss Man commented on SOLR-1559:
--------------------------------
I haven't thought through whether it would be a *good* idea or not, but we
could probably make "maxOptimizeSegments" support the full "mm" syntax fairly
easily...
http://lucene.apache.org/solr/api/org/apache/solr/util/doc-files/min-should-match.html
> maxOptimizeSegments should support percentages and negative numbers
> -------------------------------------------------------------------
>
> Key: SOLR-1559
> URL: https://issues.apache.org/jira/browse/SOLR-1559
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Hoss Man
>
> the optimize command currently supports a "maxOptimizeSegments" option which
> allows an integer to be specified resulting in a "partial optimize" down to
> that number of segments.
> This requires clients to have some visibility into the current number of
> segments. Client code could be simpler if there was an easy way to just say
> "make it smaller by some amount"
> I propose that we start supporting negative numbers and percentages as a way
> of saying "optimize down to X segments less then the current value" or
> "optimize down to X% of the current value" This could be used by "dumb"
> automatic monitors when they notice that update traffic is low, or system
> resources are idle, w/o those monitors needing to inspect the index to pick a
> good concrete number of segments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
