[VUFIND-467] Use Xincludes to separate local Solr configuration for easier management/upgrades Created: 25/Oct/11  Updated: 23/Mar/21  Resolved: 10/Sep/18

Status: Resolved
Project: VuFind®
Components: Search
Affects versions: None
Fix versions: None

Type: Improvement Priority: Major
Reporter: Demian Katz Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified


 Description   
We should investigate whether Xincludes can be used to help separate local configurations from VuFind-packaged defaults now that we have upgraded to Solr 3.4 (apparently the Xinclude functionality is stronger in 3.x than it was in 1.4).

 Comments   
Comment by Demian Katz [ 10/Sep/18 ]
Without the ability to make use of environment variable values within the XML for the purposes of including files from the right local directory, the possibilities here are limited.

Dynamic field suffixes seem to be best practice for customizing the schema without having to manage files.

For solrconfig.xml, modification of the core file still seems to be unavoidable. I would welcome anyone to reopen this ticket if they feel this is workable, but due to the current limitations, this seems like an impractical solution at this time.
Comment by Demian Katz [ 23/Mar/21 ]
While we closed this ticket as being infeasible for a general-purpose solution, University Library Tuebingen shared a local solution they use for building their Solr configurations using a combination of Xincludes, xmllint and symlinks:

https://github.com/ubtue/tuefind/tree/master/solr/vufind/biblio/conf

In particular, note generate_xml.sh, make_symlinks.sh and the xi:include in schema.xml.

This probably cannot be generalized for all VuFind users, but it may be a helpful reference for those with complex local needs.
Generated at Sat Apr 20 11:01:00 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100250-rev:2b88e55752dc82be8616a67bc2b73a87c8e22b48.