Yes, this is what I was looking for. Does the token belong to the censored principal, or to a principal within the admin group? The token needs to belong to a principal which can attach on the cluster.
Change the data_security_mode field in the cluster config to NO_ISOLATION. It's unlikely that it is related to the issues you are facing, it's more likely an issue with the configuration.But it might be worth double checking.
I tried your exact code on my environment and it worked without issue.Could it be something about the token you are using and its permissions? Is it the same token you are using for the databricks CLI? What workspace permissions does the principal ha...
Hmm, the connect info looks good to me. Can you try either of the following, see if you still get the error:Run against a cluster unconnected to Unity Catalog (put it in Access mode - No isolation shared) ORTry with an earlier runtime, ...
