influxdata / influxdata/influx-cli
Use --errors-file for more than just CSV conversion errors in `influx write`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 75
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
__Proposal:__
`influx write` should support recording more than just CSV->LP conversion errors.
__Current behavior:__
Only CSV->LP conversion errors are written to the location pointed to by `--errors-file`. Other errors are printed to console, but not persisted to file.
__Desired behavior:__
All errors encountered during writes are written to the errors-file, along with the source line that caused the problem.
__Use case:__
Help support efficiently debug & fix up bad lines during bulk data migrations
Contributor guide
No contributing guide indexed for this repository
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 by tracing the `influx write` handling of `--errors-file` and the existing CSV→LP conversion-error path. Review how other write errors and their source lines are handled; done means all errors encountered during writes are persisted to the errors file with the line that caused each problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100