BigData / Apache Hudi Interview Questions
How does Hudi achieve schema evolution?
Hudi tracks a table's schema over time and supports common evolution patterns — adding nullable columns, widening a column's type, and reordering fields — without requiring a full table rewrite, by relying on Avro-compatible schema resolution under the hood.
Because each commit on the timeline can be associated with the schema that was active when it was written, older files written under a prior schema are still read correctly: missing fields resolve to their default (typically null) and readers reconcile differences using the schema evolution rules rather than failing. This is what lets a long-running production table absorb new columns from an upstream source without a disruptive migration.
A schema evolution pattern Hudi supports without a full rewrite is:
Older files written under a prior schema are read by:
More Related questions...
