Skip to content

pin: cleanup pin indexes and storage #538

@hacdias

Description

@hacdias

Currently, the pinning/pinner package is built in such a way that the internals would technically allow for multiple pins of the same CID, while in practice that is not possible. In addition, it makes maintenance tasks or new features, such as #537, more complicated.

The idea here would be to simplify the current indexes to only having one value per key. In addition, when updates are made, avoid deleting and writing a new pin again to a different key in the datastore. Instead, reuse the same key and simply override the the information. Perhaps the ID could even be based on the CID (currently it is random).

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low: Not priority right nowdif/hardHaving worked on the specific codebase is importanteffort/daysEstimated to take multiple days, but less than a week

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions