influxdata / influxdata/influxdb
Add a "move" option to influxd upgrade
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
influxd upgrade currently makes a full copy of all V1 data, leaving the source files intact. This can prevent users from running the upgrade process if they don't have room for a full copy on their local disk.
Add a new CLI option to the upgrade command to support moving data files.
Open questions:
- Should the new option also delete the V1 meta.db and config file?
- How do we want to expose the copy-vs-move toggle in our packaging helper scripts?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the influxd upgrade command and inspect the packaging helper scripts mentioned in the issue. Determine how copy versus move should be exposed, including whether V1 meta.db and the config file are deleted. Done means the upgrade supports moving data files without requiring space for a full copy and the chosen packaging behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100