Page History

...

• Solr index format upgrade from 1.6,1.7,1.8 to 5 currently requires manual, undocumented steps (see below). 2 options:
  
  1. We automate it
     1. Seems more difficult than anticipated. There is no longer any way to easily get the Index version, as "getCurrentVersion()" has been removed (see below).
        1. updated for current version below
     - see below
  2. We document it - Currently documented in the 5.x Upgrade instructions (step #12)

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2249

  Seems like we have 2 options:
  
  1. put Tomcat-specific code to JSPUI's web.xml
  2. just document this Tomcat 7-specific warning
     On DevMtg 2014-11-05 we decided to document for RC1 and decide before RC2
     

...

DSpace 1.6 was the first version to use Solr for statistics. In order to upgrade to DSpace 5, we need to upgrade the Solr index format in two steps. The second step is easy, upgrading from DSpace 3 (Solr 3.5) to DSpace 5 means just running the Solr 4.10.4 2 optimize command, which can be run even concurrently when the UIs are running. However, Solr 4.4 doesn't understand the legacy index formats used in Solr before 3.5. Therefore, in the first step, we need to use Solr 3.5 or Lucene 3.5 to upgrade from the older index versions to 3.5.

...

We need to avoid the conflict of having both Solr 3.5 and 4.10.4 2 in the DSpace classpath. Therefore I suggest to run the first step before the Solr 4.10.4 2 webapp is started as part of DSpace 5.

To do that, we need to:

...

1. get lucene-core-3.5.0.jar from Maven Central
2. detect the index version using getCurrentVersion(index_dir) of Lucene 3.5.0
3. for any version older than LUCENE_35 go to 3, otherwise go to 6
4. run the IndexUpgrader class of Lucene 3.5 (or optimize())
5. start up DSpace in order to start up Solr 4
6. run the IndexUpgrader class of Lucene 4.10.2

• Note: Looks like the 4.4.0 version of IndexReader no longer contains this getCurrentVersion() function. It was deprecated in 3.6.0 and removed thereafter. (This is not a problem if we use the steps above)
  1. Here's a new getVersion() method

...

• 2. In case it turns out to be useful, here's how CheckIndex determines the versions on a per-segment basis: http://grepcode.com/file/repo1.maven.org/maven2/org.apache

...

• 1. .

...

• 1. lucene/

...

• 1. lucene-core

...

• 1. /4.

...

• 1. 9.0

...

• 1. /org/apache/lucene/index/CheckIndex.java#407

The manual steps would be:

...