Open tigerhawkvok opened 4 months ago
You can workaround this by enumerating every non-generated column in the "All" functions, but that kind of misses the point of both those functions and generated columns IMO. If a column is missing from the source and the target is generated, it should be skipped during validation.
I think (not actually knowing Scala) that
and
can escape the for-each assertion in those cases.
Consider this code merging data with a generated column:
Observed results
The merge fails, unable to resolve the generated column. The error will be (or close to)
[DELTA_MERGE_UNRESOLVED_EXPRESSION] Cannot resolve baz in UPDATE clause given columns foo, bar.
Expected results
The generated column is, well, generated from the inputs and as such is unnecessary to specify.
Environment information
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?