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
Avro schema evolution supports field renaming by setting the old name as an alias of the new name on the new schema.
If a field is missing on BigQuery is missing from the schema but is an alias to some other field, currently, this causes an impossible update, but there is no need to update the table schema since this is a backward-compatible schema evolution for Avro.
The text was updated successfully, but these errors were encountered:
The problem is not the data, we do use a transformer to make the data itself compatible with the previous version (a custom one).
The connector reads directly from the registry the latest version and tries to update the schema with the new column, this happens before attempting to write the data.
Avro schema evolution supports field renaming by setting the old name as an alias of the new name on the new schema.
If a field is missing on BigQuery is missing from the schema but is an alias to some other field, currently, this causes an impossible update, but there is no need to update the table schema since this is a backward-compatible schema evolution for Avro.
The text was updated successfully, but these errors were encountered: