trinodb/trino

Reuse existing view location when replacing view in Iceberg JDBC Catalog

Closed

#29,755 opened on Jun 4, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Java (2,678 forks)batch import
good first issueiceberg

Repository metrics

Stars
 (9,113 stars)
PR merge metrics
 (Avg merge 5d 9h) (306 merged PRs in 30d)

Description

Contributor guide

Research direction
Examine the referenced PR (#29729) to understand the expected behavior and identify where the view location reuse logic should be added in the Iceberg JDBC catalog code.
Tech stack
java
Domain
backenddatabasedata
Issue type
Bug
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
JavaSQLIceberg
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30