fix: drop legacy clickhouse tables and remove v1 schema#5230
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
42dfb06 to
e2335dd
Compare
e2335dd to
f8c6489
Compare
8b299ee to
67e4ad3
Compare
f8c6489 to
2fa6902
Compare
67e4ad3 to
97f9b1b
Compare
2fa6902 to
446b85f
Compare
446b85f to
db6c2a4
Compare
97f9b1b to
2846c4a
Compare
2846c4a to
03fc171
Compare
db6c2a4 to
00e420a
Compare
03fc171 to
79f77fd
Compare
00e420a to
51387fe
Compare
79f77fd to
e1740cc
Compare
51387fe to
115f800
Compare
e1740cc to
b920cc7
Compare
115f800 to
511c54a
Compare
bf0295e
into
fix/drop-v2-verification-aggregation-chain
* fix: drop v2 key verification aggregation chain from default db * fix: drop legacy clickhouse tables and remove v1 schema (#5230) * remove more stuff yippie

What does this PR do?
This PR removes all legacy ClickHouse schema definitions and adds a migration to drop the corresponding database objects. The legacy v1 schema in separate databases (
verifications,ratelimits,metrics,billing,business) is being fully replaced by the v2/v3 schema in thedefaultdatabase.The migration drops materialized views, tables, and databases in the correct dependency order to avoid foreign key constraint issues. Additionally, temporary sync materialized views that were bridging data from v1 to v2 during the migration period are also removed.
Fixes # (issue)
Type of change
How should this be tested?
defaultdatabase continues to function correctlyChecklist
Required
pnpm buildpnpm fmtmake fmton/godirectoryconsole.logsgit pull origin mainAppreciated