I'm not sure I understand the direction of resolution. I'm not saying it's
just a confusion - it's "ambiguous" and "indeterministic".
Two syntaxes were at least distinguished before Spark 3.0 by "USING ...",
and it's simply broken. I understand we are lack of time and we may need
some workaround b
Otherwise we could just set the legacy config as 'true' by default, until
SPARK-31257 (unification of create table syntax) is introduced. That would
be smallest and safest approach - no ambiguity by default, and if anyone is
adventurous or fully understanding the ambiguity they can set it to "false
