max-mapper / max-mapper/csv-join
Specify whether inner or outer join
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
For the most parts, join semantics are reasonably well covered by SQL `INNER` / `OUTER`. Basically, you want to be able to define what happens when not all rows in table A and table B can be joined. Do you keep rows? Ignore them?
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
No files, tests, or entry points are named in the issue. First clarify whether unmatched rows should be kept or discarded for inner and outer joins, then identify the relevant join implementation and tests; done means the chosen semantics are documented and verified for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100