Baseline updates differ from partial updates as follows:
To run a baseline update with production data, follow these steps:
Ensure that the Endeca HTTP Service is running on each server in the deployment environment and that you have already deployed and initialized an application.
Navigate to the control directory of deployed application. This is located under your application directory. For example:
C:\Endeca\apps\<app dir>\control.Set the
baseline_data_readyflag in the EAC by running theset_baseline_data_ready_flagscript.
You run the
partial_update script to process incremental changes in
production data and distribute the resulting index files to one or more
Dgraphs.
Ensure that the Endeca HTTP Service is running on each server in the deployment environment and that you have already deployed and initialized an application.
Navigate to the control directory of deployed application. This is located under your application directory. For example: C:\Endeca\apps\<app dir>\control.
Set the baseline_data_ready flag in the EAC by running the set_baseline_data_ready_flag script.
Specifying whether a record is included in partial updates or baseline updates
The
changePropertyNames
property specifies a property or properties of Endeca records that are examined
for changes when the records are loaded into a record store. If any of the
specified properties have changed since a record was last loaded, the entire
record will be included in the next partial update. Otherwise, the record will
be included only in baseline updates.
For more information, see Commonly edited behaviors of record stores.
