output failed tuples to stderr
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 102
- Forks
- 49
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 16
Description
By writing failed tuples to stderr, they can be collected into a file to be run again in a subsequent write command.
The expectation is to be able to call the CLI like:
fga tuple write --store-id=01H0H015178Y2V4CX10C2KGHF4 --file tuples.csv 2> failed_tuples.csv > result.json
Then it is simple to retry all failed tuples like:
fga tuple write --store-id=01H0H015178Y2V4CX10C2KGHF4 --file failed_tuples.csv
It may also be beneficial to allow the specification of an output format (e.g. json, csv, yaml).
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 CLI's tuple write entry point and trace how batch results and errors are currently emitted. Verify the command separates failed tuples on stderr from its result output on stdout, and confirm the emitted failed-tuples file can be passed back with --file for a retry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100