Yeah I don't think it's been fixed yet or is even on the roadmap to be fixed. Databricks can't prioritize fixing this bug until enough users report it. So if you can, report the issue directly with your Databricks account team.
So I was told that the Q4 date was incorrect - in fact there is currently no ETA for when this issue will be fixed. It's considered lower priority by Databricks as not enough customers are impacted or have raised this type of an issue. I would recomm...
