http://localhost/ticket/1498 <p> 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: </p> <ul><li>Better documentation on how to deploy SOLR, as single instance or multicore </li><li>A convention on how to tag schema versions and SOLR endpoints to ensure that CKAN instances point to the correct SOLR URL. </li><li>(If possible) Checks in CKAN core that deal with different schema versions. </li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1498 Trac 0.12.3 amercader Mon, 05 Dec 2011 17:57:37 GMT http://localhost/ticket/1498#comment:1 http://localhost/ticket/1498#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/1498?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket amercader Tue, 06 Dec 2011 10:04:36 GMT http://localhost/ticket/1498#comment:2 http://localhost/ticket/1498#comment:2 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> This is now done. See <a class="missing changeset" title="No default repository defined">[1]</a> 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. </p> <p> The migration work needed after releasing 1.5.1 is described in <a class="closed ticket" href="http://localhost/ticket/1516" title="task: Update SOLR schema after 1.5.1 release and set up multicore SOLR instances ... (closed: fixed)">#1516</a>. </p> <p> <a class="missing changeset" title="No default repository defined">[1]</a> <a class="ext-link" href="https://github.com/okfn/ckan/blob/feature-1498-multiple-schemas/doc/solr-setup.rst"><span class="icon">​</span>https://github.com/okfn/ckan/blob/feature-1498-multiple-schemas/doc/solr-setup.rst</a> </p> Ticket