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

Hubble 463 updates to tables for datalake backfill #258

Merged
merged 8 commits into from
Jun 27, 2024

Conversation

chowbao
Copy link
Contributor

@chowbao chowbao commented Jun 24, 2024

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with the jira ticket associated with the PR.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated the README with the added features, breaking changes, new instructions on how to use the repository. I updated the description of the fuction with the changes that were made.

Release planning

  • I've decided if this PR requires a new major/minor/patch version accordingly to
    semver, and I've changed the name of the BRANCH to release/* , feature/* or patch/* .

What

Updates to tables before doing rerun of all tables with the txmeta data lake.

  • Add ledger sequence to history_effects, history_operations, and history_assets
  • Add closed_at to history_assets
  • Add Key, Val ScVals to contract_data

Why

Certain tables are missing columns. It's better to add them now so they can be populated while doing the txmeta data lake full rerun.

Known limitations

N/A

@chowbao chowbao merged commit 84d0657 into master Jun 27, 2024
7 checks passed
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.

2 participants