Skip to content

Files Historic Plugin Retention Improvements #1372

@ata-nas

Description

@ata-nas

Story Form

As a Block Node User/Developer
I want to have a well written and resilient retention logic
So that I am confident with my retention implementation

Technical Notes

  • as mentioned in this comment thread we can improve the retention logic:
    • keep track of zips present (count)
    • modify excess calculation
    • walk the FS and delete from lowest zip found (much more resilient and less error prone)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Block NodeIssues/PR related to the Block Node.BlocksFilesHistoric PluginIssues related to the BlocksFilesHistoric PluginImprovementCode changes driven by non business requirements

    Type

    Projects

    Status

    🧊 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions