Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-5633

NoMergePolicy should have one singleton - NoMergePolicy.INSTANCE

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 4.9, 6.0
    • None
    • None
    • New, Patch Available

    Description

      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

      Attachments

        1. LUCENE-5633.patch
          42 kB
          Shai Erera

        Activity

          People

            shaie Shai Erera
            varun Varun Thacker
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment