Implement every Physical Layout
- Dominant language
- Erlang
- Stars
- 15
- Forks
- 2
- Avg merge
- 9h 58m
- Merged PRs (30d)
- 2
Description
Implement read (consume) and write (produce) support for every physical layout. In case a layout has been implemented, formally verify them with integration tests. Each layout has been tracked by a sub-issue.
See also:
- https://arrow.apache.org/docs/format/Columnar.html#physical-memory-layout
- https://github.com/apache/arrow/blob/main/format/Schema.fbs
Contributor guide
Research direction
Start by reading Apache Arrow's physical memory layout documentation and format/Schema.fbs, then use the issue's layout sub-issues to identify the individual scopes. Review the existing Erlang read and write implementations and integration tests before choosing one layout. Done means every physical layout supports consuming and producing data and has formal integration-test verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100