influxdata / influxdata/docs-v2
Create schema and samples for non-400 write request errors
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Seperately, can we have 2 separate examples so the user can delineate:
* per-line rejection (with something writtten).
* not per-rejection. Nothing written. Error message is NOT `partialWriteErrorWithRejectedPoints`. e.g. namespace errors
_Originally posted by @wiedld in https://github.com/influxdata/docs-v2/pull/5169#discussion_r1355276604_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the discussion in PR #5169 that originated this issue and locate the existing schema and write-request error documentation. Add separate examples for per-line rejection with something written and non-per-line rejection with nothing written, including a namespace error that is not `partialWriteErrorWithRejectedPoints`; done means both cases are clearly distinguishable.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100