tursodatabase / tursodatabase/libsql

`MetaStore` follow up work

Open
#768 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
17.2k
Forks
531
Avg merge
1h 12m
Merged PRs (30d)
1

Description

  • Add bottomless backup for metastore
  • Creating a new handle for a namespace that doesn't exist in the metastore should add an entry with a default config, currently it only sets the in memory representation to that. This may be fine for now but likely to be a problem in the future.
  • Potentially, use a concurrent hashmap to avoid the locking when getting a new handle which could slow down connection creation.
  • Add config settings to hello in the replication protocol to allow replica's to get the latest config from the primary.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. First split the checklist into separate proposals and inspect the metastore and replication-protocol implementations before defining scope. Done should be specified independently for backup support, namespace persistence, handle-concurrency behavior, and replica configuration exchange.

Written by the indexing model from the issue text.

Assessment

Domain
databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.