As discussed offline, this is a change but not a breaking one because if this `insert into foo (a) values (1)` command fails in Spark 3.3, but now succeeds, it is changing an error case into a successful case. This is part of the intentional behavior change of the column DEFAULT project.