Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Iceberg] Bump Iceberg Version to 1.12

Aperta
#4,547 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@polyzos ci sta già lavorando.

Dal 14/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java

Direzione di ricerca

Start by reading the linked FIP-31 proposal and tracing the current Iceberg plugin, build and packaging setup, and union-read savepoint handling. The community must first resolve the plugin transition, savepoint migration, and REST scan-planning decisions. Done means the chosen upgrade builds and passes the stated compatibility, migration, integration, packaging, and documentation checks.

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

Descrizione

component=lake
Search before asking
  • I searched in the issues and found nothing similar.
Description

Iceberg 1.12 was just released I'm Fluss can upgrade to it.

Upgrading to the latest iceberg, will allow Fluss users to use Iceberg with Flink 2.2 and Flink 2.3 because the current Iceberg 1.10 only supports up to Flink 2.1, which Fluss doesn't.

However Iceberg 1.12 requires Java 17.
The upgrade should preserve Fluss's existing Java requirements outside the new Iceberg plugin. Every JVM loading that plugin, including Fluss servers and Flink jobs, must use Java 17+.

Scope
  • Update the dependency and replace the removed GenericAppenderFactory API.
  • Use a JDK 17 toolchain to build and test the new plugin while keeping the main build and release process on JDK 11.
  • Provide a migration path for union-read savepoints. The current state embeds Java-serialized Iceberg objects that are incompatible across these versions; the proposed replacement is a versioned JSON format.
  • Close catalogs after use, verify plugin classloading, align dependencies, and update packaging and license notices.
  • Document supported Java/Flink versions, matching Iceberg jars, and upgrade steps.
Decisions Needed

Agree on these in the community discussion before finalizing the implementation:

  1. Keep a Java 11-compatible Iceberg 1.10 plugin during a transition, or replace it immediately? If retained, choose the default plugin and support window.
  2. Require savepoints for plugin switches, with a migration release before switching existing state to 1.12?
  3. Support REST server-side scan planning in this upgrade, or reject it with a clear error until supported?
Acceptance Criteria
  • The new plugin builds and runs on Java 17 without raising Java requirements for other Fluss users.
  • Unit and integration tests pass for the documented engine versions and packaged plugin.
  • Savepoint migration is tested with partially consumed data; rollback is tested if both plugins are retained.
  • REST catalog and S3 integration tests pass, and catalogs close without leaking resources.
  • Release packaging, notices, and compatibility documentation are updated.

Iceberg v3 features and deletion vectors are separate follow-up work.

Willingness to contribute
  • I'm willing to submit a PR!
Lingua principale
Java
Stelle
2.2k
Fork
656
Merge medio
2g 16h
PR unite (30g)
103

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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/fluss

Tutte le issue di apache/fluss

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.