Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-3141

Warn in logs at Optimize (was: Deprecate OPTIMIZE command in Solr)

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.5
    • 5.5, 6.0
    • update

    Description

      Background: LUCENE-3454 renames optimize() as forceMerge(). Please read that issue first.

      Now that optimize() is rarely necessary anymore, and renamed in Lucene APIs, what should be done with Solr's ancient optimize command?

      Attachments

        1. SOLR-3141.patch
          2 kB
          Jan Høydahl
        2. SOLR-3141.patch
          1.0 kB
          Yonik Seeley
        3. SOLR-3141.patch
          0.6 kB
          Yonik Seeley

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LUCENE-3454 rename optimize to a less cool-sounding name

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SOLR-7733 remove "optimize" from the UI.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Task - A task that needs to be done. SOLR-3146 Create migration guide from 3.x to 4.0

          • Major - Major loss of function.
          • Closed

          Activity

            People

              janhoy Jan Høydahl
              janhoy Jan Høydahl
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: