Ticket #1498 (closed enhancement: fixed)
Support multiple SOLR schema versions
Reported by: | amercader | Owned by: | amercader |
---|---|---|---|
Priority: | major | Milestone: | ckan-sprint-2011-12-05 |
Component: | ckan | Keywords: | solr search |
Cc: | Repository: | ckan | |
Theme: | migrations |
Description (last modified by amercader) (diff)
At some point the SOLR schema used by CKAN will need to be changed and the changes won't be always backward compatible, so we need a mechanism to support instances that use older versions of the schema. This process will involve:
- Better documentation on how to deploy SOLR, as single instance or multicore
- A convention on how to tag schema versions and SOLR endpoints to ensure that CKAN instances point to the correct SOLR URL.
- (If possible) Checks in CKAN core that deal with different schema versions.
Change History
comment:2 Changed 2 years ago by amercader
- Status changed from new to closed
- Resolution set to fixed
This is now done. See [1] for the deployment documentation and conventions. CKAN checks the remote schema version on startup to see if it's compatible. See commits starting from 50285ef6.
The migration work needed after releasing 1.5.1 is described in #1516.
[1] https://github.com/okfn/ckan/blob/feature-1498-multiple-schemas/doc/solr-setup.rst
Note: See
TracTickets for help on using
tickets.