[ 
https://issues.apache.org/jira/browse/LUCENE-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Lef updated LUCENE-4323:
-------------------------------

    Attachment: LUCENE-4323.patch

Sorry about that. I had eclipse do some auto-formatting on save, so the patch 
included more than it should have. Updated patch is attached (no tabs).
                
> Add max cfs segment size to LogMergePolicy and TieredMergePolicy
> ----------------------------------------------------------------
>
>                 Key: LUCENE-4323
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4323
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>    Affects Versions: 4.0-BETA
>            Reporter: Alexey Lef
>            Priority: Minor
>         Attachments: LUCENE-4323.patch
>
>
> Our application is managing thousands of indexes ranging from a few KB to a 
> few GB in size. To keep the number of files under control and at the same 
> time avoid the overhead of compound file format for large segments, we would 
> like to keep only small segments as CFS. The meaning of "small" here is in 
> absolute byte size terms, not as a percentage of the overall index. It is ok 
> and in fact desirable to have the entire index as CFS as long as it is below 
> the threshold.
> The attached patch adds a new configuration option maxCFSSegmentSize which 
> sets the absolute limit on the compound file segment size, in addition to the 
> existing noCFSRatio, i.e. the lesser of the two will be used. The default is 
> to allow any size (Long.MAX_VALUE) so that the default behavior is exactly as 
> it was before.
> The patch is for the trunk as of Aug 23, 2012.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to