Pluggable Backend Interface with DataFusion for Bounded-Memory Compute

Aperta
#3,715 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
python

Direzione di ricerca

Non vengono indicati file di implementazione o test. Inizia leggendo le issue correlate #1210, #3270 e #3554, quindi definisci l’ambito dei protocolli ReadBackend, WriteBackend e ComputeBackend proposti e dell’integrazione con DataFusion. Il lavoro è completato quando sono implementati i comportamenti elencati di eliminazione, streaming, ordinamento e pianificazione delle scansioni, non ci sono regressioni senza DataFusion e i risultati di PyArrow e DataFusion sono equivalenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

PyIceberg uses PyArrow as its sole execution engine. PyArrow is a kernel library with no memory management, no spill-to-disk, and no join operators. Operations that process more data than available memory (CoW deletes, equality delete resolution, scan planning for heavily-deleted tables, sorted writes) crash with OOM errors.

This issue tracks introducing a pluggable backend interface (ReadBackend, WriteBackend, ComputeBackend protocols) and integrating Apache DataFusion as the first bounded-memory compute backend.

Problem

Operation Current Status OOM Pattern
Equality delete reads Hard ValueError Anti-join requires all delete keys in memory
CoW delete (large files) OOMs Materializes entire Parquet file into RAM
Scan planning (>100K deletes) OOMs All delete entries in Python dict
Sort-on-write Not implemented Full sort before write
Positional deletes (millions) OOMs Python set of positions

Tables written by Flink (which uses equality deletes) are completely unreadable by PyIceberg today.

Solution

  1. Pluggable interface: ReadBackend, WriteBackend, ComputeBackend protocols that decouple PyIceberg from PyArrow
  2. DataFusion integration: Bounded-memory sort, join, and filter with spill-to-disk via datafusion-python
  3. Migration: All existing data operations route through the interface with zero API changes

Deliverables

  • Equality delete resolution (NEW): tables with equality deletes can now be read
  • CoW delete/overwrite streaming (FIX): statistics short-circuit + two-pass streaming
  • Positional delete resolution (IMPROVED): bounded-memory for large delete sets
  • Sort-on-write (NEW): external merge sort when DataFusion installed
  • Bounded-memory scan planning (NEW): for tables with >100K delete files

Related Issues

  • #1210 - Support reading equality delete files
  • #3270 - Equality Delete support
  • #3554 - Integrate DataFusion as execution engine

Acceptance Criteria

  • All existing tests pass without datafusion installed (no regression)
  • Tables with equality deletes return correct results
  • CoW delete on 2GB+ files completes without OOM (with DataFusion)
  • Sort-on-write produces sorted files when table has sort order and DataFusion installed
  • Property-based tests verify PyArrow and DataFusion backends produce identical output
Lingua principale
Python
Stelle
1.1k
Fork
589
Merge medio
2g 4h
PR unite (30g)
72

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/iceberg-python

Tutte le issue di apache/iceberg-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.