Consider adding support for more column types in the filter2 API
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
such as String columns as convenience over Binary columns, Maps, Sets, etc.
Maybe we don't want to do this and just support the primitive column types though.
**Reporter**: [Alex Levenson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alexlevenson) / @isnotinvain
**Note**: *This issue was originally created as [PARQUET-35](https://issues.apache.org/jira/browse/PARQUET-35). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the filter2 API and the migration documentation linked in the issue. Clarify whether String, Map, and Set columns are in scope or whether support should remain limited to primitive types; completion requires an agreed scope and corresponding support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100