Page History
...
- Solr index format upgrade from 1.6,1.7,1.8 to 5 currently requires manual, undocumented steps (see below). 2 options:
- We automate it -
- Seems more difficult than anticipated. There is no longer any way to easily get the Index version, as "getCurrentVersion()" has been removed (see below).
- updated for current version below
- Seems more difficult than anticipated. There is no longer any way to easily get the Index version, as "getCurrentVersion()" has been removed (see below).
- We document it - Currently documented in the 5.x Upgrade instructions (step #12)
- We automate it -
Seems like we have 2 options: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 - put Tomcat-specific code to JSPUI's web.xml
- just document this Tomcat 7-specific warning
On DevMtg 2014-11-05 we decided to document for RC1 and decide before RC2
...
- detect the index version using getCurrentVersion(index_dir)
- 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
- Here's a new getVersion() method
- 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
- for any version older than LUCENE_35 go to 3, otherwise go to 6
- get lucene-core-3.5.0.jar from Maven Central
- run the IndexUpgrader class of Lucene 3.5 (or optimize())
- start up DSpace in order to start up Solr 4
- run the IndexUpgrader class of Lucene 4.4
...
Overview
Content Tools