Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Current »

Overview

This page documents the use of admin tools to rebuild the Lucene index.  Indexes are created based on the hibernate-search annotations on model objects such as @Indexed, @IndexedEmbedded, @Field, @ContainedIn, etc.

Prerequisites

  • MySQL database must already exist (e.g. "tsdb").  
    • If no data exists in the database, this tool will clear the indexes.
    • Otherwise, it will index the available data.
  • MySQL database connection parameters must be defined in the properties file specified by "run.config.ts".
  • The file system directory specified by the "hibernate.search.default.indexBase" in the properties file specified by run.config.ts must exist.

Details

This tool is used to rebuild Lucene indexes for objects indexed by the system.

Indexes are written into the directory specified by the hibernate.search.default.indexBase property in the properties file specified by "run.config.ts".

Following are some details about the implementation of this tool:

Mojo: LuceneReindexMojo.java (in admin/mojo/src/main/resources/java/org/ihtsdo/otf/ts/mojo)

Project: admin/lucene

Configuration Parameters

  • run.config.ts - the standard configuration file specified as a -D parameter

  • indexed.objects - optional parameter that allows a comma-separated list of objects to reindex (e.g. MapRecordJpa).  If omitted, all indexes are rebuilt.

  • server - this (default false) flag indicates whether the mojo should be run in standalone mode or against a running server.  A server check ensures the intended mode is the current case (e.g. if server is false, but the base.url specified in run.config.ts is running a server, then the mojo will fail - as well as the inverse where the server flag is true but a server is not running at base.url)  

Samples

Sample command line call of the admin tool to rebuild all indexes:

 

% cd ~/code/admin/lucene
% mvn install -PReindex -Drun.config.ts=/home/ec2-tomcat/config/config.properties

 

Sample command line call of the admin tool to rebuild all indexes via a REST call to the server (here the run.config.ts is used to specify the base.url parameter, which is where the server is running):

 

% cd ~/code/admin/lucene
% mvn install -PReindex -Drun.config.ts=/home/ec2-tomcat/config/config.properties -Dserver=true

 

 

Sample command line call of the admin tool to reindex only certain data types:

 

# Re-indexes only map records and tracking records
% cd ~/code/admin/lucene
% mvn install -PReindex -Drun.config.ts=/home/ec2-tomcat/config/config.properties -Dindexed.objects=ConceptJpa

 

Sample eclipse run configuration to rebuild all indexes:

Troubleshooting

Occasionally it is necessary to completely reindex all objects from scratch. When this is needed, the recommended approach is to remove the index files from the index and then run this mojo. For example:

 

# stop the server
% service tomcat7 stop
 
# remove the index
% /bin/rm -rf /var/lib/tomcat7/indexes/*ConceptJpa
 
# rebuild the index
% cd ~/code/admin/lucene
% mvn install -PReindex  -Drun.config.ts=/home/ec2-tomcat/config/config.properties -Dindexed.objects=ConceptJpa
 
# start the server
% service tomcat7 start

 

  • No labels