API improvements for Arrow arrays
- Dominant language
- C#
- Stars
- 39
- Forks
- 30
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 16
Description
### Describe the enhancement requested
A number of improvements have been suggested over the years to improve the Arrow APIs. Some of these would be backwards-incompatible.
- Implement `IEqualityComparer`
- Implement `IEqualityComparer`
- Fix implementation of `IEquatable` on arrays
- Standardize on a base class instead of an interface
- Add pretty-printing methods
- Define scalar types for all Arrow types
- `FixedSizeBinaryArray` somehow ended up in namespace `Apache.Arrow.Arrays` instead of `Apache.Arrow` like the other arrays.
[https://github.com/apache/arrow/issues/21197](https://github.com/apache/arrow/issues/21197)
[https://github.com/apache/arrow/issues/21748](https://github.com/apache/arrow/issues/21748)
[https://github.com/apache/arrow/issues/21992](https://github.com/apache/arrow/issues/21992)
[https://github.com/apache/arrow/issues/36777](https://github.com/apache/arrow/issues/36777)
[https://github.com/apache/arrow/issues/45095](https://github.com/apache/arrow/issues/45095)
Contributor guide
Research direction
The issue names several unrelated Arrow API improvements and links issues 21197, 21748, 21992, 36777, and 45095, but no files or tests. Start by reviewing those linked issues and agreeing on one narrowly scoped change; done should mean that one improvement has a defined implementation and validation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100