smithoss/gonymizer

Mechanism for reducing dump size by limiting rows per table?

Open

#52 opened on Sep 10, 2019

View on GitHubContributor guide
 (3 comments) (0 reactions) (1 assignee)Go (34 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (160 stars)
PR merge metrics
 (PR metrics pending)

Description

Thanks for this tool. It looks pretty great.

I'd like to both anonymize my data as well as decrease the size of the overall database size. Is there a mechanism such that I could specify a maximum number of records for a particular table, and delete any records prior to that maximum set?

Contributor guide

Research direction
Examine the existing dump code to understand how tables are exported, then implement a new flag (e.g., max rows per table) that truncates each table to the specified row count before anonymization.
Tech stack
gopostgresql
Domain
databasebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
GoPostgreSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60