Wout
Contributor

@Debayan Mukherjee​ @Lindsay Olson​ I believe this is a bug in Databricks SQL. Could you please pass this on to second-level/next-level support?