cockroachdb / cockroachdb/cockroach
Provide insights for bulk delete scenarios
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
This issue tracks providing an external user insight when [best practices](https://www.cockroachlabs.com/docs/stable/bulk-delete-data.html) are not followed when bulk deleting data. For instance, large DELETEs (e.g., millions of rows) should have an insight to break down the operation.
Jira issue: CRDB-26434
Contributor guide
Research direction
No source files, tests, or entry points are named. Start by reading the linked bulk-delete best practices and Jira issue CRDB-26434, then locate CockroachDB's existing insight mechanism and determine how bulk DELETE operations should be detected and reported; done means large operations produce the intended external insight.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100