Serge Smertin

Thank you for the feature request! Currently, the team operates in a limited capacity, carefully prioritizing, and we cannot provide a timeline to implement this feature. Please make a Pull...

@mattfysh can you also post the cluster config? most likely it's already fixed by ae3cb3fcca7c3554c3d4d231666f000ee5761fc5

@pietern yes, with `Retry-After` from platform we'd go through https://github.com/databricks/databricks-sdk-py/blob/main/databricks/sdk/retries.py#L35-L39 but now I want it to go through https://github.com/databricks/databricks-sdk-py/blob/main/databricks/sdk/retries.py#L40-L41 All of transient errors eventually have to go away - https://github.com/databricks/databricks-sdk-py/blob/main/databricks/sdk/core.py#L1096-L1102,...

> Why not retry on all 429s? @pietern we can, sure, preferably after https://github.com/databricks/databricks-sdk-py/pull/376 is merged. it'll be straightforward to add `except TooManyRequests as err: if err.retry_after_seconds is not None:...

There’s a PR to ignore pagination-related fields for iterators. And there’s discussion either or not we do “virtual iteration” for scim lists

@mgyucht CLI subprocess takes 700ms per call (because `az` is in Python), slowing down an app.

Please make PRs to the relevant OpenAPI specs

Could you link to protocol description? We don’t really want to depend on any external liberties, as much as possible. Simply because of transitive dependency tree size.

@mgyucht https://github.com/databricks/databricks-sdk-go/blob/main/.codegen/api.go.tmpl#L219-L221 i think we need to change this to `max_results` "virtual field", that would do a "global limit". Or we can keep the `limit` name, but redefine the semantics...

@mgyucht it's orthogonal to #543 (we should hold on that because of the upcoming language changes - https://github.com/golang/go/issues/61405). this change is about cross-SDK semantics on removing low-level fields to paginated...