Skip to content

feat(streams): expose maxUniquePropertiesWithData & consumption - #2919

Draft
andersfylling wants to merge 3 commits into
masterfrom
andersf/streams/hvd-1482-unique-properties-usage
Draft

andersfylling wants to merge 3 commits into
masterfrom
andersf/streams/hvd-1482-unique-properties-usage

Conversation

@andersfylling

Copy link
Copy Markdown
Contributor

Description

Allows users to estimate how much more they can ingest before hitting their capacity.

andersfylling and others added 3 commits November 4, 2026 04:32
Streams have a cap on the number of unique properties that can hold data,
but SDK users had no way to see a stream's own cap or how much of it is
used, so they could not tell how much property capacity a stream has left
before writes start failing. The streams API now returns this as
settings.limits.uniquePropertiesWithData (alpha), so surface it on
StreamLimitSettings and request it from the stream endpoints.

HVD-1482

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…_data

The API exposes this limit as maxUniquePropertiesWithData, in line with the
other per-stream limits (maxRecordsTotal, maxGigaBytesTotal) and with the same
key in the stream template listing, so the SDK field follows that name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The expanded Args section added noise to the diff without being needed for
the new field.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant