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
Schema evolution in INSERT doesn't always work properly when the new column is added to a struct nested within an array or map. If another column is renamed, the operation fails when it should succeed.
Steps to reproduce
For example with a map, in python, renaming column key to renamed_key and added a field comment in the a struct inside the map:
The operation succeeds, the table schema is changed to key int, metrics map<string, struct<id: int, value: int, comment: string>> and the data is inserted.
Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?
Yes. I can contribute a fix for this bug independently.
Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
No. I cannot contribute a bug fix at this time.
The text was updated successfully, but these errors were encountered:
Bug
Describe the problem
Schema evolution in INSERT doesn't always work properly when the new column is added to a struct nested within an array or map. If another column is renamed, the operation fails when it should succeed.
Steps to reproduce
For example with a map, in python, renaming column
key
torenamed_key
and added a fieldcomment
in the a struct inside the map:Note that the struct inside the map isn't evolved to add the new field. Without the unrelated column being renamed, this works well:
Observed results
The operation fails.
Expected results
The operation succeeds, the table schema is changed to
key int, metrics map<string, struct<id: int, value: int, comment: string>>
and the data is inserted.Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?
The text was updated successfully, but these errors were encountered: