On this page:

6.2Lucene Indexing


Smile CDR uses Apache Lucene to provide fast indexing capabilities for specific query patterns that benefit from this type of index. Using this feature is completely optional, and Smile CDR will function without it.

However, its use can significantly improve performance and enable additional functionality on terminology operations, so it is recommended for use in environments where validation or other terminology operations will be heavily used. For more information, see Terminology and Lucene Indexing.


When Lucene Indexing is enabled, one or more of the following indexes should be enabled:

  • Terminology Index – The terminology index stores CodeSystem concept details, including codes, properties, and hierarchy in a specialized index that can be used for efficient code searches.

  • FullText Content Index – The FullText Content index indexes all string element values within every resource stored to the repository. This can be useful in allowing fulltext searches, but it can potentially consume a large amount of space so careful capacity planning should be used if this feature is enabled on a repository that contains large a number of resources.

  • Search Parameter Index – The Search Parameter index extends token indexing with support for the :text modifier, as well as indexing string parameters with support for the :exact, :contains, and :text search modifiers. This will increase space and memory requirements.

Lucene Providers

Smile CDR ships with compatibility to 3 providers that can be used to provide indexing services. Each one has its own characteristics:

  • LUCENE_MEMORY – This provider keeps a copy of the index in memory. This provider is only recommended for testing and non-production scenarios. It is very fast, but will lose all stored data when the system shuts down.

  • LUCENE_DISK – This provider uses a local disk file to store indexing information. This option is a production-ready solution, but is only recommended for non-clustered environments.

  • ELASTICSEARCH – This provider uses an Elasticsearch cluster to provide indexing. This option is suitable for clustered environments. Note that to use this option, you will need to create your own Elasticsearch cluster.

6.2.1Lucene Disk Provider


When using the Lucene Disk Provider, a directory on the local filesystem should be configured using the Hibernate Search Directory option.

This directory should be created on a disk partition that has enough capacity to store all content for the selected indexes.

6.2.2Elasticsearch Provider


When using the Elasticsearch provider, the following settings should be provided:

  • URL – The Elasticsearch Cluster endpoint URL stripped of protocol

  • Protocol – The Elasticsearch

  • Username – The Elasticsearch connection username.

  • Password – The Elasticsearch connection password.