Solr
  1. Solr
  2. SOLR-3146

Create migration guide from 3.x to 4.0

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: None
    • Fix Version/s: 4.2, 5.0
    • Component/s: documentation
    • Labels:
      None

      Description

      Spinoff from SOLR-3141:

      Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road. Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred to explicit commit, which is also a huge mistake many people do, they do over-committing!

        Issue Links

          Activity

          Hide
          Jan Høydahl added a comment -

          Resolving as not a problem. CHANGES.TXT was probably enough

          Show
          Jan Høydahl added a comment - Resolving as not a problem. CHANGES.TXT was probably enough
          Hide
          Otis Gospodnetic added a comment -

          Is this still needed, considering Solr 4.0 has been out for a over a month now and we haven't seen a ton of issues...?

          Show
          Otis Gospodnetic added a comment - Is this still needed, considering Solr 4.0 has been out for a over a month now and we haven't seen a ton of issues...?
          Hide
          Torin Danil added a comment -

          I think there are a lot of features in upcoming lucene4: starting with NRTManager, and ending with automata support (with whole shebang of regexp queries, fast fuzzy and spellcheck)

          All of these need to have hooks in SOLR (I might be mistaken, but from what I've seen in trunk, those are completely missing)

          So I think it's acceptable that old solr users won't get new features, just some sane defaults, but to experience the full power of new release will be required to migrate.

          Show
          Torin Danil added a comment - I think there are a lot of features in upcoming lucene4: starting with NRTManager, and ending with automata support (with whole shebang of regexp queries, fast fuzzy and spellcheck) All of these need to have hooks in SOLR (I might be mistaken, but from what I've seen in trunk, those are completely missing) So I think it's acceptable that old solr users won't get new features, just some sane defaults, but to experience the full power of new release will be required to migrate.
          Hide
          Yonik Seeley added a comment -

          So I've thought about changing to soft commits by default too. Here's the issue:
          People use commit to make their recent updates visible (and a NRT softCommit would now be most appropriate).
          But commit also flushes all segments to disk and syncs them, and in a master-slave scenario causes index changes to be replicable.

          One possibility is to add a softCommit default of true to the normal update handlers.
          People migrating an existing solrconfig wouldn't get that default, but new users (or users starting from scratch with the new solrconfig would).

          I don't know if it's worth it or not though. Thoughts?

          Show
          Yonik Seeley added a comment - So I've thought about changing to soft commits by default too. Here's the issue: People use commit to make their recent updates visible (and a NRT softCommit would now be most appropriate). But commit also flushes all segments to disk and syncs them, and in a master-slave scenario causes index changes to be replicable. One possibility is to add a softCommit default of true to the normal update handlers. People migrating an existing solrconfig wouldn't get that default, but new users (or users starting from scratch with the new solrconfig would). I don't know if it's worth it or not though. Thoughts?
          Hide
          Jan Høydahl added a comment -

          Perhaps a page on the WIKI, and when mature, move to CMS?

          Show
          Jan Høydahl added a comment - Perhaps a page on the WIKI, and when mature, move to CMS?

            People

            • Assignee:
              Unassigned
              Reporter:
              Jan Høydahl
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development