Using a merge policy for incremental updates

A merge policy determines how frequently the Dgraph merges incremental update generations in its data files, for a specific data store.

The data layer stores the data files of an Endeca data store as a series of internal files with versions. As a result:

A version is persisted as a sequence of generation files. A new version appends a new generation file to the sequence. Query latency depends, in part, on the number and size of generation files used to store the data files.

Generation files are combined through a process called merging. Merging is a background task that does not affect the Endeca data store features, but may affect its performance. Because of this, you can set a merge policy that dictates the aggressiveness of the merges. In a clustered environment, merge policy can be set on the leader node only.