qziyuan
qziyuan
There is not a good solution for a DBSQL query to tell if the workspace is UC enabled or not. For now we have to bear with this error, but...
@zpappa do you have the issue created for the "code migration"? I have customers asking helps to change the 2 level namespace to 3 level namespace in their queries and...
Agree, we should create access connector in this case.
1. PR #2409 will fix 1st `Endpoint security policy is required and must be one of NONE, DATA_ACCESS_CONTROL, PASSTHROUGH.` error. 2. The 2nd `enable_serverless_compute is required.` error is pending upstream...
So any code that calls [`AccountClient.get_workspace_client`](https://github.com/databricks/databricks-sdk-py/blob/6a9c534e39e8bb447725d6cdf3612549849f0bdd/databricks/sdk/__init__.py#L935) with SDK v0.29.0 will have this error. With that, following commands in UCX v0.28.0 and above will suffer from this issue: - `create-account-groups` command...
[ES-1203418](https://databricks.atlassian.net/browse/ES-1203418) is filed to fix the SDK bug.
The upstream bug fix is being tracked in this ES ticket https://databricks.atlassian.net/browse/ES-1203418 @ouranos meanwhile you can try the workaround above to run `sync-workspace-info`, or instead use `manual-workspace-info`
To whom do not have access to https://databricks.atlassian.net/browse/ES-1203418, here is the update: A PR is created to fix the `cannot pickle '_thread.lock'`. However it will cause a regression that each...
> No proper ucx build is available till now. For every version there is some issues. Others are also getting same issues? @sagpra My customer tried today and the workaround...