Skip to content

Comments

[cluster] Update collection for subscribe results#35055

Draft
bkirwi wants to merge 5 commits intoMaterializeInc:mainfrom
bkirwi:update-collection
Draft

[cluster] Update collection for subscribe results#35055
bkirwi wants to merge 5 commits intoMaterializeInc:mainfrom
bkirwi:update-collection

Conversation

@bkirwi
Copy link
Contributor

@bkirwi bkirwi commented Feb 17, 2026

No description provided.

@github-actions
Copy link

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

@bkirwi bkirwi force-pushed the update-collection branch 3 times, most recently from 0eb840c to 4d52aec Compare February 24, 2026 00:03
I've implemented this or similar a few times now... time to share.
This lets us remove some implementation, including some unsafe.
This code previously resorted and reallocated data in ~all cases. We now
do more or less the minimum for the given subscribe format.
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