You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
pluma:
When accessing a cursor from the HTTP API (reading the next batch), is the ttl reset or will it still expire according to the initial ttl? IOW, does the ttl set a total cursor lifetime or just a "dead man's switch" for inactivity? (the HTTP API docs don't explain this, btw, they only mention ttl when creating the cursor). It looks like it does (from manual testing) but the docs don't indicate this.
jsteemann:
The TTL is renewed every time the cursor is accessed.
The text was updated successfully, but these errors were encountered:
pluma:
When accessing a cursor from the HTTP API (reading the next batch), is the ttl reset or will it still expire according to the initial ttl? IOW, does the ttl set a total cursor lifetime or just a "dead man's switch" for inactivity? (the HTTP API docs don't explain this, btw, they only mention ttl when creating the cursor). It looks like it does (from manual testing) but the docs don't indicate this.
jsteemann:
The TTL is renewed every time the cursor is accessed.
The text was updated successfully, but these errors were encountered: