Add documentation of the `rethinkdb export` format
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
@Tryneus wrote this great writeup to describe the format of the backup files that rethinkdb export generates.
https://github.com/rethinkdb/rethinkdb/issues/3503#issuecomment-68910513
I think we should include this in our documentation (though it's not high priority).
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
Read the format writeup in issue #3503, comment 68910513, then locate the appropriate backup or export section in the RethinkDB documentation repository. Incorporate the writeup as documentation for files generated by rethinkdb export; done means the export format is available in the published docs and remains consistent with the referenced description.
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
- 55/100