Page History
...
| Option | Release | Repo content | Features | Installation Process | Migration Process | Schema Update Process | Management | Notes | ||
|---|---|---|---|---|---|---|---|---|---|---|
| Deploy Solr as Docker Image | 7.preview | New cores only | single server | Core created on container startup Core persisted in docker volumes | N/A | None. A fresh install is required. | N/A | |||
| Standalone Solr (new cores) | 7.preview | New cores only | single server | Ant fresh install script needed | N/A | None. Schema update will not be supported until 7.0 | DSpace 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 | Manually deploy schema updates to Solr. | DSpace sysadmin | ||
| 8.0+ | New cores Migrated cores No shards | single server | TBD. Note future configuration options. | |||||||
| Solr Cloud | 7.0 | New cores Migrated cores "Time Routed Aliases" instead of shards | multi server | DBA 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 manually deploys schema updates to Solr. | DBA | ||
| 8.0+ | New cores Migrated cores "Time Routed Aliases" instead of shards | multi server | TBD. Note future configuration options.DBA |
Related Tickets and Pull Requests
...
Overview
Content Tools