Skip to content

Document migrating data to a new aggregate - #290

Closed
reeceyang wants to merge 1 commit into
reece/safe-clear-allfrom
reece/aggregate-migration-docs
Closed

reeceyang wants to merge 1 commit into
reece/safe-clear-allfrom
reece/aggregate-migration-docs

Conversation

@reeceyang

@reeceyang reeceyang commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Adds a README section on moving an aggregate's data into a new aggregate while the app keeps running: dual-write with the idempotent methods, backfill from the table or copy from the old aggregate, verify, switch reads, then clean up. Also covers the pitfalls found while testing this end to end on a local deployment: verifying against the table rather than the old aggregate, keeping a new aggregate out of an unprefixed aggregate's component, and deleting the old component from the dashboard, since unmounting it keeps its data.

Stack

🤖 Generated with Claude Code

@pkg-pr-new

pkg-pr-new Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@convex-dev/aggregate@290

commit: a736a06

@reeceyang
reeceyang force-pushed the reece/aggregate-migration-docs branch from f96b8b0 to 89970e9 Compare November 14, 2026 05:49
@reeceyang
reeceyang changed the base branch from reece/namespace-prefix to reece/safe-clear-all November 14, 2026 05:49
@reeceyang

Copy link
Copy Markdown
Contributor Author

From Claude: closing in favor of the named-aggregates approach in #292 and #278.

@reeceyang reeceyang closed this Nov 17, 2026
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