[parquet-thrift] improve performance of thrift push-down code
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
A user reported seeing slowness when projection push-down code is active, which seems to stem from ProtocolEventsAmender.
Details can be found in https://github.com/Parquet/parquet-mr/issues/406
**Reporter**: [Dmitriy V. Ryaboy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dvryaboy) / @dvryaboy
#### PRs and other links:
- [GitHub Pull Request #7](https://github.com/apache/parquet-mr/pull/7)
**Note**: *This issue was originally created as [PARQUET-7](https://issues.apache.org/jira/browse/PARQUET-7). 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 projection push-down path around ProtocolEventsAmender and read the details in issue #406. Review the referenced pull request #7 to understand the existing work; done means resolving the reported slowness when projection push-down is active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100