Skip to content
This repository was archived by the owner on Jul 31, 2023. It is now read-only.
This repository was archived by the owner on Jul 31, 2023. It is now read-only.

Separate partitions by table in SQL-based storage backends. #114

Description

@tylerwilding-wk

Currently we store all data in a single table, eva_kv, we should partition data by table instead.

Tables, in a sense, act as partitions / groupings of data already, and have tools surrounding them for that purpose. These tools likely align with a lot of our concerns, but we cannot use them directly right now.

It's easier to consider / reuse tooling with something like a table acting as our partition (for sql at least), since the semantics for move this table from database A to database B or drop this table are much easier to get right than, say, move the set of rows matching this criteria or delete the set of rows matching this criteria from this table

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions