yugabyte/yugabyte-db

[DocDB] Help users map snapshot schedules to dbs more clearly when using yb-admin restore_snapshot_schedule

Open

#16,190 opened on Feb 22, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C (1,003 forks)batch import
area/docdbgood first issuekind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-5622

Description

To perform pitr, a user must pass a snapshot schedule's uuid to the yb-admin restore_snapshot_schedule command. The command doesn't provide any output indicating which database was restored.

To make things easier for users we should modify the command so the link between snapshot schedule and db is clear. The command could possibly be modified to support a db name, or it could print out the name of the db restored when it returns successfully.

Contributor guide

Research direction
Examine the yb admin restore snapshot schedule command implementation to add output of the restored database name or allow passing a database name as a parameter.
Tech stack
ccpp
Domain
databasecli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
basic understanding of yb admin CLI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70