trinodb/trino

Resolve deprecations in Parquet

Open

#1,802 opened on Oct 18, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (9,113 stars) (2,678 forks)batch import
good first issuemaintenance

Description

presto-orc has very few deprecation warnings and these are probably unavoidable (related to #37)

however presto-parquet has many more. We should resolve them, as they often signal upcoming breaking changes.

Contributor guide

Tech stack
java
Domain
databackend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaParquet file formatTrino internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Focus on the presto parquet module in the Trino repository. Identify all deprecation warnings reported during compilation or runtime. Each warning should be investigated to determine the replacement API. The linked issue #37 may provide context on unavoidable deprecations. Check if there are any maintainer comments in the issue or existing PRs that clarify the desired approach.