You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Carry over manifest stat maps decoded by the reader (#38)
The Avro reader decodes Iceberg stat maps as arrays of {key, value}
records rather than plain objects; boundForField in prune.js already
handles both shapes on the read side. encodeMap only handled the object
form, so writeExistingDeleteManifest threw "expected bigint value" out of
avroWrite whenever it carried over an entry that had come back from a
manifest with stats on it.
Real delete files carry those stats: the Spark and Java position delete
files under test/files/hyperparam-iceberg/*/bunnies both have
lower_bounds, and the Java equality delete file has value_counts as well.
Icebird alone never reached this, since v3 refuses to write new position
delete files and v2 refuses to write deletion vectors, so the two only
coexist on an upgraded table or one another engine wrote. The added test
covers that case.
0 commit comments