What causes "Unexpected delete file content: " in apache/iceberg?

Align the Iceberg runtime version used by Flink with the version that wrote the table's delete files (avoid mixed Iceberg jars on the classpath).

apache/iceberg · error · IllegalArgumentException

Unexpected delete file content:

Error message

Unexpected delete file content:

What it means

TableChange aggregates per-checkpoint changes to an Iceberg table for the Flink maintenance (compaction) pipeline. When summarizing DataFile/DeleteFile changes, it switches on the file content type; a DeleteFile whose content is neither EQUALITY_DELETES nor POSITION_DELETES (nor a data case) has no handling branch, so the switch's default throws this IllegalArgumentException to fail fast rather than silently miscounting deletes.

Source

Thrown at flink/v2.1/flink/src/main/java/org/apache/iceberg/flink/maintenance/operator/TableChange.java:85

    dataFiles.forEach(
        dataFile -> {
          this.dataFileCount++;
          this.dataFileSizeInBytes += dataFile.fileSizeInBytes();
        });

    deleteFiles.forEach(
        deleteFile -> {
          switch (deleteFile.content()) {
            case POSITION_DELETES:
              this.posDeleteFileCount++;
              this.posDeleteRecordCount += deleteFile.recordCount();
              break;
            case EQUALITY_DELETES:
              this.eqDeleteFileCount++;
              this.eqDeleteRecordCount += deleteFile.recordCount();
              break;
            default:
              throw new IllegalArgumentException("Unexpected delete file content: " + deleteFile);
          }
        });

    this.commitCount = 1;
  }

  static TableChange empty() {
    return new TableChange(0, 0L, 0, 0L, 0, 0L, 0);
  }

  public static Builder builder() {
    return new Builder();
  }

  int dataFileCount() {
    return dataFileCount;
  }

View on GitHub (pinned to 86d9c8fc54)

Solutions

Align the Iceberg runtime version used by Flink with the version that wrote the table's delete files (avoid mixed Iceberg jars on the classpath).
Inspect the delete file's content() value and confirm the table spec/format version is one the maintenance operator supports.
Upgrade the Iceberg Flink runtime to a release that handles the new delete content type.
If the file is genuinely corrupt, remove/rewrite the offending delete file via a rewrite or repair procedure.

Defensive patterns

Strategy: validation

Validate before calling

if (deleteFile.content() != FileContent.EQUALITY_DELETES && deleteFile.content() != FileContent.POSITION_DELETES) {
  throw new IllegalStateException("Unsupported delete content on table: " + deleteFile.content());
}

Type guard

boolean isSupportedDelete(DeleteFile f) {
  return f.content() == FileContent.EQUALITY_DELETES || f.content() == FileContent.POSITION_DELETES;
}

Try / catch

try { tableChange = new TableChange(...); } catch (IllegalArgumentException e) { LOG.error("Unsupported delete file content; check Iceberg version alignment", e); }

Prevention

Keep Iceberg runtime versions identical across writers, Flink jobs, and maintenance topologies.
Pin the Iceberg version in your build and avoid shaded/mixed jars on the cluster classpath.
Before enabling maintenance on a table written by other tools, scan its delete file content types.

When it happens

Trigger: Constructing a TableChange from DeleteFile entries where a file's content() returns a value outside the handled cases — e.g. a new/unknown DeleteFileContent enum value from a newer Iceberg format version, or a corrupt/incorrectly-typed DeleteFile passed into the TableChange constructor.

Common situations: Running the Flink maintenance topology against a table written by a newer Iceberg version introducing new delete content types; corrupted metadata listing malformed delete files; classpath mixing Iceberg versions so enum constants mismatch.

Related errors

AI-assisted analysis of apache/iceberg@86d9c8fc54 (2026-09-12). Data as JSON: /api/errors/0a5dbc87bbef2011. Report an issue: GitHub.