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.

Sign up for GitHub

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

Jump to bottom

Remove legacy store adapters & fix prune of stake pool & epoch settings #1076

Merged
merged 8 commits into from
Jul 26, 2023
Merged

Remove legacy store adapters & fix prune of stake pool & epoch settings #1076

merged 8 commits into from
Jul 26, 2023

Commits on Jul 26, 2023

  1. Use directlyCertificateRepository instead of the CertificateStore

    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    fd252ca View commit details
    Browse the repository at this point in the history

  2. Use directly EpochSettingStore instead of the ProtocolParameterStore

    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    a7f27b3 View commit details
    Browse the repository at this point in the history

  3. Fix prune when saving for EpochSettingStore 

    It did not execute at all since the cursor wasn't consumed.
    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    e19e019 View commit details
    Browse the repository at this point in the history

  4. Fix prune when saving for StakePoolStore 

    It did not execute at all since the cursor wasn't consumed.
    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    a7a0711 View commit details
    Browse the repository at this point in the history

  5. Increase STAKE_POOL_PRUNE_EPOCH_THRESHOLD to 10 

    In order to have some breath if something goes wrong while pruning
enough data to keep that table lean.
    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    eaeee84 View commit details
    Browse the repository at this point in the history

  6. Use retention limit from configuration instead of constants 

    This allow to synchronise pruning between tables, else pruning of data
can occurs from tables that is used as a foreign key in another.
Also, enable data pruning in the e2e tests for the aggregator in order
to test it.
    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    8f555da View commit details
    Browse the repository at this point in the history

  7. Add safe_epoch_retention_limit to Configuration 

    In order to ensure that if a retention limit is set it's not lower than
a minimum value in order to not prune data that will be used at later
epochs.
    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    cbfe804 View commit details
    Browse the repository at this point in the history

  8. Update versions

    @Alenar
    Alenar committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    ef9c487 View commit details
    Browse the repository at this point in the history