yugabyte/yugabyte-db

[DocDB] The term "apply" is overloaded

Open

#15,280 opened on Dec 9, 2022

View on GitHub
 (0 comments) (0 reactions) (1 assignee)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-4441

Description

In our code, the word "apply" could mean any of the following things:

  • Applying Raft records to the underlying state machine (RocksDB)
  • Applying intents to regular RocksDB (reading from intents DB and writing to the regular RocksDB)

Perhaps we should rename "applying" transactions to "settling" transactions.

Contributor guide

Research direction
Identify all uses of 'apply' in transaction context and rename to 'settle' to reduce ambiguity.
Tech stack
c
Domain
databasebackend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
GitC programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70