We are having the same issues. This is 100% definitely a bug in Databricks 12.2. Just changing an existing cluster from 11.3 to 12.2 (without touching anything else) results in those errors: "Resolved attribute(s) ... missing from ..." and "Attribute(s) with the same name appear in the operation".