In order to upgrade to the Solr 4 search service, whilst the Solr 4 indexes are being
built, you must transition from a previous version of SkyVault Community Edition (for example,
version 4.2.x) with the Solr 1.4 search service to SkyVault Community Edition
5.2 with the Solr 1.4 search
service.
- Install SkyVault Community Edition 5.2 with both the Solr 1.4 and Solr 4 search services.
-
From your old Solr 1.4 installation, copy all the indexes to the new Solr 1.4
installation.
- Copy the alf_data/solr/workspace/SpacesStore/index directory from the old Solr 1.4 installation to the alf_data/solr/workspace/SpacesStore/index directory of the new Solr 1.4 installation.
- Copy the alf_data/solr/archive/SpacesStore/index directory from the old Solr 1.4 installation to the alf_data/solr/archive/SpacesStore/index directory of the new Solr 1.4 installation.
-
Reapply the configuration changes made to the solrcore.properties
file of the old Solr 1.4 installation to the solrcore.properties file
of the new Solr 1.4 installation.
- Reapply the changes made to the alf_data/solr/workspace-SpacesStore/conf/solrcore.properties file from the old Solr 1.4 installation to the alf_data/solr/workspace-SpacesStore/conf/solrcore.properties file of the new Solr 1.4 installation.
- Reapply the changes made to the alf_data/solr/archive-SpacesStore/conf/solrcore.properties file from the old Solr 1.4 installation to the alf_data/solr/archive-SpacesStore/conf/solrcore.properties file of the new Solr 1.4 installation.
- Ensure that your SkyVault Community Edition 5.2 instance is set to use Solr 1.4 search service during this process.
To validate that your old Solr 1.4 indexes and configuration changes are correctly
copied over to the new Solr 1.4 installation, follow these steps:
- Run SkyVault Community Edition 4.x with the old Solr 1.4 installation and SkyVault Community Edition 5.2 with the new Solr 1.4 installation at the same time.
- Generate the SUMMARY report for both the old and the new Solr indexes.
- Compare the two SUMMARY reports to ensure that both have the same number of nodes, transactions, and ACLs.