About the last read generation for a client

A Record Store instance can save the last read generation and also track that generation for any number of unique clients. You specify a unique client by creating a client ID, which can be any string, such as rsreader1, and then set a value to indicate the last-read generation for that client ID. If you are using Integrator, you can use the default client ID of Integrator.

There are two ways to set the last read generation for a client:

Automatically, in an Integrator ETL graph, by using a Record Store Reader component to read records from the Record Store. In the component, set IAS Client ID to specify the client ID for the generation that is being read in.
Manually, by using the set-last-read-generation task of the Record Store command-line utility.

Here is an example using Integrator to process the records:

You run a full IAS crawl and it writes the records to a Record Store as Generation 1.
You run an Integrator ETL graph using Generation 1. You set the Record Store Reader component with a IAS Read Type of Full Extract and a IAS Client ID of Integrator.
You run a second IAS crawl, either full or incremental, and store the records as Generation 2. Because both crawls use the same idPropertyName and the same seeds, some of the records in both generations are identical and the others are delta records (new, modified, or deleted records).
You run an Integrator ETL graph using the delta records between Generation 1 and Generation 2. For this graph, you set the Record Store Reader component with a IAS Read Type of Incremental and a IAS Client ID of Integrator.
The Integrator ETL graph processes the delta records.

To find out which client states are currently saved in a Record Store instance, use the list-client-states task of the Record Store Command-line Utility.