Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  •  Complete upgrade of client code to SolrJ 7_x.
  •  Remove the dspace-solr artifact.
  •  Work out manual steps for installing empty cores in a free-standing Solr (for a new installation).
  •  See what manual steps can be moved into Ant's fresh_install scripts.
  •  Determine whether schema updates are required.
  •  Create dump/restore or migration tools for indexes which cannot be recreated (statistics, authority).
  •  Work out manual steps for copying/migrating/recreating cores with index records into a free-standing Solr.
  •  See what manual steps can be moved into Ant's update scripts.  This is only for transition from our outdated dspace-solr artifact to current stock Solr.
  •  Document the changes to DSpace fresh installation:  set up Solr separately if you don't already have it, install cores.
  •  Document the process for moving existing indexes to free-standing Solr during a DSpace upgrade from 6_x.

Solr Deployment Options

OptionReleaseRepo contentFeaturesInstallation ProcessMigration ProcessSchema Update ProcessManagementNotes
Deploy Solr as Docker Image7.previewNew cores onlysingle server

Core created on container startup

Core persisted in docker volumes

N/ANone. A fresh install is required.N/A
Standalone Solr (new cores)7.previewNew cores onlysingle serverAnt fresh install script neededN/ANone. Schema update will not be supported until 7.0DSpace sysadmin
Standalone Solr (new or migrated cores)7.0

New cores

Migrated cores

No shards

single server

Ant fresh install script needed

Auto detection of existing core needed

Migration script needed for statistics and authority.

Does this run as part of the install process or is this a maintenance script?

Is this a migration process or an import process?

Deploy new schema file?

Once a new schema is in place, what process brings existing records up to date?

DSpace sysadmin
Solr Cloud7.0

New cores

Migrated cores

"Time Routed Aliases" instead of shards

multi serverDBA creates cores and installs schemas

Migration script needed for statistics and authority.

Does this run as part of the install process or is this a maintenance script?

Performed by DBA?DBA


Related Tickets and Pull Requests

...