Improve Parquet Protobuf Usability
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Check out the PR for details.
- Move away from passing around a `Class` object to take advantage of Java Templating
- Make parquet-proto library more usable and straight-forward
- Provide test examples
- Limited support for protocol buffer schema registry
**Reporter**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
**Assignee**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
**Note**: *This issue was originally created as [PARQUET-1903](https://issues.apache.org/jira/browse/PARQUET-1903). 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 with the pull request referenced in the issue and inspect the parquet-proto API, since no source files or tests are named here. Done would mean a more straightforward Java-templated API, test examples, and limited protocol buffer schema registry support as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100