[enhancement] option for createReadStream() to return nodes in the reverse order that they were added.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 748
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
I have been looking into adding an option into the iterator but it does look non-trivial.
Before the release of 3.0.0-0 I had been using my own createReadStream from within hyper-graph-db - https://github.com/e-e-e/hyper-graph-db/blob/master/lib/hyperdbModifier.js. It returned keys in reverse order to which they were added by the user. Thinking about it - I am not sure if this is 100% important but still wanted to raise it as a potential enhancement.
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 locating the createReadStream iterator in hyperdb and compare its behavior with lib/hyperdbModifier.js in hyper-graph-db. Determine how insertion order is represented and where an option could be introduced. Done means createReadStream can optionally return nodes in reverse insertion order without changing its existing default behavior, with coverage for both orders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100