Page tree
Skip to end of metadata
Go to start of metadata


Documents the indexing strategy.


The domain objects are annotated to integrate with the Hibernate-search framework which combines the persistence mechanisms of Hibernate JPA with Lucene indexing. Annotations on getter methods indicate which fields are to be indexed, whether the values are to be tokenized, and whether they are actually stored in the index.  

In the current configuration, all identifier and textual fields are indexed.  Text fields are analyzed and identifiers are not.  Wherever a text field is analyzed, a corresponding field called "xxxSort" also exists which is not analyzed so that it can be used for Lucene-based sorting.

Indexes are generated for the following objects:

  • LogEntry

  • MemoryEntryJpa

  • PhraseMemoryJpa

  • ProjectJpa 

  • RefsetJpa 

  • ReleaseInfoJpa

  • TranslationJpa 

  • UserJpa

  • ConceptJpa 

  • ConceptRefsetMemberJpa

  • DescriptionJpa

  • TrackingRecordJpa

These indexes support the various modes of searching within the application.  

Fielded searches into these objects are supported.  For each object type, the getter methods with @Field annotations support indexing with an index field name matching the getter field name (e.g. getWorkflowStatus translates to a field of "workflowStatus").  Where @IndexEmbedded annotations are used, nested fields can also be performed (e.g. for a map record you can search the field "entries.targetId").

For information on reindexing, see the admin tool page: Reindex Objects


The following configuration settings affect how search works.

Default Value

EDIT_THIS/mapping/lucene/indexesThe indexing strategy uses a filesystem-based index. This is the configuration setting for the directory where the index files live. the style of indexing strategy.
  • No labels