Row format: support omitting null byte for non-nullable types
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 1.3k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 168
Description
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
For primitives, the row format
**Describe the solution you'd like**
When given a datatype that is not nullable, we don't have to write the first byte (`1_u8`) as every value will be valid. This saves some time / memory usage.
We can add a field / constructor to `SortField`.
**Describe alternatives you've considered**
**Additional context**
See slack question/discussion: https://the-asf.slack.com/archives/C01QUFS30TD/p1692631551160779
Contributor guide
Research direction
Start by locating the row-format implementation and the SortField definition or constructors mentioned in the issue. Trace how nullability is encoded for primitive values and identify the existing tests for row serialization. Done means non-nullable types can omit the leading null byte while nullable types retain the current format, with coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100