Support rewrite_manifests table maintenance

Open
#3,629 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
databases

Research direction

Locate the Python table maintenance/API entry point corresponding to Table.rewriteManifests(); read the current snapshot and manifest-management paths first. Done means an explicit operation regroups current manifests, preserves sequence numbers and V3 first_row_id, marks rewritten entries EXISTING, and commits a replace snapshot.

Written by the indexing model from the issue text.

Description

Feature Request / Improvement

Rewriting manifests without changing data speeds up scan planning when a table has accumulated many small manifests. Java exposes this as Table.rewriteManifests() (Spark: rewrite_manifests).

Scope: an explicit maintenance operation that reads the current snapshot's manifests, regroups entries, rewrites them preserving sequence numbers (entries rewritten as EXISTING) and, for V3, first_row_id, and commits a replace snapshot. Related: #270 tracks automatic manifest merging on write; this covers the explicit maintenance API.

Dominant language
Python
Stars
1.1k
Forks
589
Avg merge
2d 4h
Merged PRs (30d)
72

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/iceberg-python

All issues in apache/iceberg-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.