events: Add events hypertable #8561
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Yopi
force-pushed
the
yopi/events/timescaledb-2
branch
4 times, most recently
from
837e730 to
ef61122
Compare
We create a shadow copy of the events table, that we make into a timescaledb hypertable. We will double write to both events table for a period of time until we are ready to drop the old events table.
Yopi
force-pushed
the
yopi/events/timescaledb-2
branch
from
ef61122 to
2fb36f8
Compare
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.
We create a shadow copy of the events table, that we make into a timescaledb
hypertable. We will double write to both events table for a period of time
until we are ready to drop the old events table.
Initially we let the hypertable be bucketed by week, this can be changed going forward if
the event volumes pick up.
The
events_hypertable is a 1:1 copy of theeventstable, except the foreign key references since that is not supported by timescaledb.