Pinning data versions

The Dgraph process of the Endeca Server maintains knowledge about loaded records using the index. Since the index can be updated continuously, at any given time, several data versions of the index are maintained in memory. In some cases, it may be useful for the front-end applications (such as Studio), to issue queries against a specific data version. This process is known as "pinning a data version".

Using two optional operations in the Conversation Web Service, and the settings for timeouts in the EndecaServer.properties file, you can:

Pin a data version for a specified timeout. Once the timeout expires, the data version is dismissed by the Endeca Server.
Issue queries while requesting a previously pinned data version. If the queries are issued within the timeout period, they use the pinned version. The timeout is renewed from the time of the last valid request that used the pinned version.
Pin a version, wait and pin it again with a longer timeout period that is still less than the maximum timeout listed in EndecaServer.properties. In this case, the timeout is renewed to a longer timeout you specify.