Hi Mark

Thanks for response. You write "If true eager errors are essential, consider lobbying Databricks support for feature restoration." Do you know where I can lobby / send in suggestions to Databricks?

I'm also curious if you, as a Databricks employee, have any info about whether Databricks plans to document this change, or restore the old behavior? But it's fair enough if you don't have that info.

Thank you for your help once again