[
https://issues.apache.org/jira/browse/LUCENE-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-5633.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.0
4.9
Assignee: Shai Erera
Lucene Fields: New,Patch Available (was: New)
Committed to trunk and 4x. Thanks Varun!
> NoMergePolicy should have one singleton - NoMergePolicy.INSTANCE
> ----------------------------------------------------------------
>
> Key: LUCENE-5633
> URL: https://issues.apache.org/jira/browse/LUCENE-5633
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Varun Thacker
> Assignee: Shai Erera
> Priority: Minor
> Fix For: 4.9, 5.0
>
> Attachments: LUCENE-5633.patch
>
>
> Currently there are two singletons available - MergePolicy.NO_COMPOUND_FILES
> and MergePolicy.COMPOUND_FILES and it's confusing to distinguish on compound
> files when the merge policy never merges segments.
> We should have one singleton - NoMergePolicy.INSTANCE
> Post to the relevant discussion -
> http://mail-archives.apache.org/mod_mbox/lucene-java-user/201404.mbox/%3CCAOdYfZXXyVSf9%2BxYaRhr5v2O4Mc6S2v-qWuT112_CJFYhWTPqw%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
