Merging Indexes

Two or more indexes can me merged using IndexDeployer command line tool. Merging indexes usually provides much better performance when you have multiple indexes deployed.

Important: All merged indexes must have the same text analysis settings.

Index merging

Usage example:

  IndexDeployer -i c:/QuestAgent/IndexProfiles/coll1/ -ml merge-list.txt -o c:/merged/index/deployed

The parameter -ml specifies a merge list. It’s a plain text file listing indexes for merging and their identifier:

 coll1=c:/work/QuestAgent/IndexProfiles/coll1/
 coll2=c:/work/QuestAgent/IndexProfiles/coll2/

Notice that slash is used as a path separator on the Windows too, as an alternative to escaped back-slashes.

Collection identifiers specified in the merge list will be built into the deployed index and can not be changed later.

Index specified as an input index using `-i` option will be used as a template index from which text analisys settings will be copied to the resulting index. This index should be specified in the merge list too.

Using merged index in search applet

Use applet parameter `collections.index` to specify path to the merged collections. Merged index can not be used in combination with other indexes (which will be ignorred).

Example configuration:

 collections = all coll1 coll2
 collections.index = qagent8/data/merged
 collection.coll1.name = Publication 1
 collection.coll1.locationPrefix = coll1/

 collection.coll2.name = Publication 2
 collection.coll2.locationPrefix = coll2/

 collection.all.name = All publications

Collection with identifier `all` is a special case that enables search in the complete index.