Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(blobstorage): isolating tables for no blob data duplication #16702

Merged
merged 3 commits into from
Apr 10, 2024

Conversation

k-kaddal
Copy link
Contributor

@k-kaddal k-kaddal commented Apr 9, 2024

This pr handles solution to avoid blob data duplication, by splitting the blob_hashes table into blob_hashes and blocks_meta tables.

  • Database migration: creating blocks_meta table and migrating data
  • Database migration: creating a new blob_hashes table with unique blob_hash, migrating old data to the new blob_hashes
  • Implementing a BlocksMetaRepository
  • Implementing a database transaction for storing the blob and block data
  • Implementing a database transaction for deleting blobs and blocks based on the blockId
  • Fixing the indexer accordingly

@k-kaddal k-kaddal self-assigned this Apr 9, 2024
@k-kaddal k-kaddal changed the title feat(blobstorage): database migration for creating blocks_meta table … feat(blobstorage): isolating tables for no blob data duplication Apr 9, 2024
@cyberhorsey cyberhorsey added this pull request to the merge queue Apr 10, 2024
Merged via the queue into main with commit 55426ef Apr 10, 2024
6 checks passed
@cyberhorsey cyberhorsey deleted the feat/blobstorage-blocks_meta-table branch April 10, 2024 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants