performance: Use upstream optimizations
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 7
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Description
In light of upstream changes we should avoid using the SimpleTransformIterator here to be able to take full advantage of them
@jacoscaz @rubensworks
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 reading the linked upstream AsyncIterator issue and locating the asyncjoin code that uses SimpleTransformIterator. Compare the upstream optimizations with the current join implementation, then verify that the join still behaves correctly while no longer depending on SimpleTransformIterator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100