Clarify hypercore migration guidance for existing hypertables#292
Open
atovpeko wants to merge 2 commits into
Open
Clarify hypercore migration guidance for existing hypertables#292atovpeko wants to merge 2 commits into
atovpeko wants to merge 2 commits into
Conversation
✅ Checklist CompleteThank you for taking the time to properly review your PR! All checklist items are complete. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
Adds an "Enable hypercore on an existing hypertable" section to
setup-hypercore.mdxcovering the two recommended paths for converting a populated hypertable to the columnstore:add_columnstore_policy(notes the policy runs single-threaded and may lag on a large backlog).convert_to_columnstoreper chunk, with an explicit parallel-sessions sample for faster initial migration.Also adds a warning callout explaining that conversion takes an
ExclusiveLockon the chunk and contends with concurrent backfill — links to the existing pause-backfill-reconvert workflow onconvert_to_rowstore.Extends the
convert_to_columnstorereference page with a bulk-migration sample showing the same parallel pattern.Why: Review feedback flagged that the docs were missing recommended paths for migrating existing hypertables and didn't mention lock contention between conversion and backfill. Behavior was verified against the TimescaleDB 2.27.0 source (
tsl/src/compression/api.c:658forExclusiveLock,sql/policy_internal.sql:93-121for the serial policy loop) and end-to-end on a live Tiger Cloud service.Affected pages
Related Issues
Issue: #EDU-131
Checklist before requesting a review