General requirements for partial and baseline updates

This section lists the general requirements for baseline and partial updates.

Baseline updates are needed for configuration changes.

Periodically run baseline updates to ensure that the index representation in the MDEX Engine is in sync with those configuration changes that can be applied only with a baseline update, such as dictionary changes or wildcarding.
Partial updates require a separate partial update pipeline to process the update files. You also start the MDEX Engine with an additional command-line flag.
All records in the partial update pipeline must be identified by a single record specifier property that is unique for each record.
Baseline updates must not overlap. A new baseline cannot be started until processing of the prior baseline has been completed (completed means that the baseline update has been loaded into the MDEX Engine).
Baseline and partial updates must not overlap. Do not run a baseline update at the same time as a partial update, since both processes use the autogen_dimensions.xml file that can be accessed by only one process at a time.