Skip to content

store/metadata: Update docs with recent changes #86

Open

Activity

  1. metalmatze commented on Feb 9, 2022

    @metalmatze
    Member

    Copied from Slack:

    Hello, I’m messing about with Parca today on my 20% time, and I was just wondering… The docs say

    for now, we’re using a SQLite in-memory by default
    https://www.parca.dev/docs/storage

    but it looks like you’re using Badger by default, which to my admittedly limited understanding is a KV store
    https://github.com/parca-dev/parca/blob/v0.7.1/pkg/parca/parca.go#L73

  2. Dean-Coakley commented on Jun 24, 2022

    @Dean-Coakley

    Looks like this can be closed as it was resolved in: #128 ?

  3. brancz commented on Jun 24, 2022

    @brancz
    Member

    We actually just changed this again which made the updated docs stale again. The organization of keys is thoroughly documented here though: https://github.com/parca-dev/parca/blob/main/pkg/metastore/kv.go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestgood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions