Skip to content

Conversation

@polyzos
Copy link
Contributor

@polyzos polyzos commented Jan 18, 2026

No description provided.

}
}

public void startKeepAlivePeriodically(int keepAliveIntervalMs) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where do we plan to start to start keepalives? This method seems currently unused.

Separately, I wonder if we're giving clients too much control over holding server resources with keepalives. I can see issue where clients forget to close and server starts leaking iterators.

Should we simplify and get rid of keepalives and refresh iterator TTL on server side whenever a ScanKvRequest is made?

It's a two-way door to release this feature without keepalive. We cannot easily remove keepalive mechanism once added as it would break clients who rely on keepalive mechanism.

* Creates a new {@link SnapshotQuery} for this table to configure and execute a snapshot query
* to read all current data in a table bucket (requires to be a Primary Key Table).
*/
SnapshotQuery newSnapshotQuery();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: SnapshotQuery sounds like querying an existing snapshot. I cannot think of any name though.. maybe just Query?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants