Problem
The Iceberg v2/v3 manifest specification requires every manifest Avro file to include a schema-id key in its file metadata. Icebird currently writes schema, partition-spec, partition-spec-id, format-version, and content, but omits schema-id.
Affected writer paths in src/write/manifest.js:
Spec reference: Manifest metadata requirements. The table marks schema-id as required for v2 manifests; v3 retains this requirement.
Expected behavior
Each writer should include:
"schema-id": String(schema["schema-id"])
in the Avro file metadata, and manifest round-trip tests should assert that the value is present for both v2 and v3 output.
This is a pre-existing compliance gap identified while reviewing #39; it is not caused by that PR.
Problem
The Iceberg v2/v3 manifest specification requires every manifest Avro file to include a
schema-idkey in its file metadata. Icebird currently writesschema,partition-spec,partition-spec-id,format-version, andcontent, but omitsschema-id.Affected writer paths in
src/write/manifest.js:writeDataManifestwriteDeleteManifestwriteExistingDataManifest(added by Add writeExistingDataManifest for manifest rewrites #39)writeExistingDeleteManifestSpec reference: Manifest metadata requirements. The table marks
schema-idas required for v2 manifests; v3 retains this requirement.Expected behavior
Each writer should include:
in the Avro file metadata, and manifest round-trip tests should assert that the value is present for both v2 and v3 output.
This is a pre-existing compliance gap identified while reviewing #39; it is not caused by that PR.