...
- Search index must be deployed separately from VIVO
- Connection from VIVO to search index must be over HTTP
- Failure to connect to search index on start-up must be non-fatal
- VIVO must not require a restart in order to connect to search index that was not available on VIVO's initial startup
- VIVO SmokeTest must make it clear to the user that VIVO is in a non-functional state while a search index is not available
- Externalized search index must provide the same results as the previous, embedded Solr index
Related tickets
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1589 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1592 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1596 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1600 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1612 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1611 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1590