Customizing the Index Schema
The default solr
index schema delivered with
the Content Engine is optimized for editorial purposes: it indexes
all the fields needed to support the search functionality provided by
Content Studio, resulting in very large indexes. This is
acceptable in the editorial context, since the number of concurrent
Content Studio users, even in a very large organisation, is not
likely to be very large. The presentation hosts
in a large Escenic installation, however, can be required to serve
many thousands of concurrent users, and the default
solr
configuration may perform poorly in this
context.
In other words, the default configuration is fine for the editorial hosts in a production system, but for the presentation hosts you are recommended create a custom indexer configuration that only indexes the fields actually needed to support the kinds of search required in your publications.
To do this, open var/lib/escenic/schema.xml
for editing on each of your presentation hosts,
and modify the index schema to meet your requirements. Editing this
file is outside the scope of this manual. In order to tune the search
engine you need to take account of both the contents of your
publications, your users' needs with regards to search and the
limitations imposed by your particular hardware configuration. For
further information and advice on tuning, see the Solr documentation
on http://lucene.apache.org/solr/.