hotdata 0.3.1__tar.gz → 0.4.1__tar.gz

{hotdata-0.3.1 → hotdata-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hotdata
-Version: 0.3.1
+Version: 0.4.1
 Summary: Hotdata API
 Author-email: Hotdata <developers@hotdata.dev>
 License: MIT

{hotdata-0.3.1 → hotdata-0.4.1}/hotdata/__init__.py

@@ -37,7 +37,6 @@ __all__ = [
     "QueryRunsApi",
     "RefreshApi",
     "ResultsApi",
-    "SandboxesApi",
     "SavedQueriesApi",
     "SecretsApi",
     "UploadsApi",
@@ -85,7 +84,6 @@ __all__ = [
     "CreateEmbeddingProviderRequest",
     "CreateEmbeddingProviderResponse",
     "CreateIndexRequest",
-    "CreateSandboxRequest",
     "CreateSavedQueryRequest",
     "CreateSecretRequest",
     "CreateSecretResponse",
@@ -105,7 +103,6 @@ __all__ = [
     "DatasetSourceOneOf4",
     "DatasetSummary",
     "DatasetVersionSummary",
-    "DeleteSandboxResponse",
     "DiscoveryStatus",
     "EmbeddingProviderResponse",
     "Error",
@@ -115,6 +112,7 @@ __all__ = [
     "GetDatasetResponse",
     "GetResultResponse",
     "GetSecretResponse",
+    "IndexEntryResponse",
     "IndexInfoResponse",
     "IndexStatus",
     "InformationSchemaResponse",
@@ -131,11 +129,11 @@ __all__ = [
     "ListDatasetVersionsResponse",
     "ListDatasetsResponse",
     "ListEmbeddingProvidersResponse",
+    "ListIndexesPageResponse",
     "ListIndexesResponse",
     "ListJobsResponse",
     "ListQueryRunsResponse",
     "ListResultsResponse",
-    "ListSandboxesResponse",
     "ListSavedQueriesResponse",
     "ListSavedQueryVersionsResponse",
     "ListSecretsResponse",
@@ -155,8 +153,6 @@ __all__ = [
     "RefreshWarning",
     "ResultInfo",
     "ResultsFormatQuery",
-    "Sandbox",
-    "SandboxResponse",
     "SavedQueryDatasetSource",
     "SavedQueryDetail",
     "SavedQuerySummary",
@@ -175,7 +171,6 @@ __all__ = [
     "UpdateDatasetResponse",
     "UpdateEmbeddingProviderRequest",
     "UpdateEmbeddingProviderResponse",
-    "UpdateSandboxRequest",
     "UpdateSavedQueryRequest",
     "UpdateSecretRequest",
     "UpdateSecretResponse",
@@ -203,7 +198,6 @@ from hotdata.api.query_api import QueryApi as QueryApi
 from hotdata.api.query_runs_api import QueryRunsApi as QueryRunsApi
 from hotdata.api.refresh_api import RefreshApi as RefreshApi
 from hotdata.api.results_api import ResultsApi as ResultsApi
-from hotdata.api.sandboxes_api import SandboxesApi as SandboxesApi
 from hotdata.api.saved_queries_api import SavedQueriesApi as SavedQueriesApi
 from hotdata.api.secrets_api import SecretsApi as SecretsApi
 from hotdata.api.uploads_api import UploadsApi as UploadsApi
@@ -255,7 +249,6 @@ from hotdata.models.create_dataset_response import CreateDatasetResponse as Crea
 from hotdata.models.create_embedding_provider_request import CreateEmbeddingProviderRequest as CreateEmbeddingProviderRequest
 from hotdata.models.create_embedding_provider_response import CreateEmbeddingProviderResponse as CreateEmbeddingProviderResponse
 from hotdata.models.create_index_request import CreateIndexRequest as CreateIndexRequest
-from hotdata.models.create_sandbox_request import CreateSandboxRequest as CreateSandboxRequest
 from hotdata.models.create_saved_query_request import CreateSavedQueryRequest as CreateSavedQueryRequest
 from hotdata.models.create_secret_request import CreateSecretRequest as CreateSecretRequest
 from hotdata.models.create_secret_response import CreateSecretResponse as CreateSecretResponse
@@ -275,7 +268,6 @@ from hotdata.models.dataset_source_one_of3 import DatasetSourceOneOf3 as Dataset
 from hotdata.models.dataset_source_one_of4 import DatasetSourceOneOf4 as DatasetSourceOneOf4
 from hotdata.models.dataset_summary import DatasetSummary as DatasetSummary
 from hotdata.models.dataset_version_summary import DatasetVersionSummary as DatasetVersionSummary
-from hotdata.models.delete_sandbox_response import DeleteSandboxResponse as DeleteSandboxResponse
 from hotdata.models.discovery_status import DiscoveryStatus as DiscoveryStatus
 from hotdata.models.embedding_provider_response import EmbeddingProviderResponse as EmbeddingProviderResponse
 from hotdata.models.error import Error as Error
@@ -285,6 +277,7 @@ from hotdata.models.get_database_context_response import GetDatabaseContextRespo
 from hotdata.models.get_dataset_response import GetDatasetResponse as GetDatasetResponse
 from hotdata.models.get_result_response import GetResultResponse as GetResultResponse
 from hotdata.models.get_secret_response import GetSecretResponse as GetSecretResponse
+from hotdata.models.index_entry_response import IndexEntryResponse as IndexEntryResponse
 from hotdata.models.index_info_response import IndexInfoResponse as IndexInfoResponse
 from hotdata.models.index_status import IndexStatus as IndexStatus
 from hotdata.models.information_schema_response import InformationSchemaResponse as InformationSchemaResponse
@@ -301,11 +294,11 @@ from hotdata.models.list_databases_response import ListDatabasesResponse as List
 from hotdata.models.list_dataset_versions_response import ListDatasetVersionsResponse as ListDatasetVersionsResponse
 from hotdata.models.list_datasets_response import ListDatasetsResponse as ListDatasetsResponse
 from hotdata.models.list_embedding_providers_response import ListEmbeddingProvidersResponse as ListEmbeddingProvidersResponse
+from hotdata.models.list_indexes_page_response import ListIndexesPageResponse as ListIndexesPageResponse
 from hotdata.models.list_indexes_response import ListIndexesResponse as ListIndexesResponse
 from hotdata.models.list_jobs_response import ListJobsResponse as ListJobsResponse
 from hotdata.models.list_query_runs_response import ListQueryRunsResponse as ListQueryRunsResponse
 from hotdata.models.list_results_response import ListResultsResponse as ListResultsResponse
-from hotdata.models.list_sandboxes_response import ListSandboxesResponse as ListSandboxesResponse
 from hotdata.models.list_saved_queries_response import ListSavedQueriesResponse as ListSavedQueriesResponse
 from hotdata.models.list_saved_query_versions_response import ListSavedQueryVersionsResponse as ListSavedQueryVersionsResponse
 from hotdata.models.list_secrets_response import ListSecretsResponse as ListSecretsResponse
@@ -325,8 +318,6 @@ from hotdata.models.refresh_response import RefreshResponse as RefreshResponse
 from hotdata.models.refresh_warning import RefreshWarning as RefreshWarning
 from hotdata.models.result_info import ResultInfo as ResultInfo
 from hotdata.models.results_format_query import ResultsFormatQuery as ResultsFormatQuery
-from hotdata.models.sandbox import Sandbox as Sandbox
-from hotdata.models.sandbox_response import SandboxResponse as SandboxResponse
 from hotdata.models.saved_query_dataset_source import SavedQueryDatasetSource as SavedQueryDatasetSource
 from hotdata.models.saved_query_detail import SavedQueryDetail as SavedQueryDetail
 from hotdata.models.saved_query_summary import SavedQuerySummary as SavedQuerySummary
@@ -345,7 +336,6 @@ from hotdata.models.update_dataset_request import UpdateDatasetRequest as Update
 from hotdata.models.update_dataset_response import UpdateDatasetResponse as UpdateDatasetResponse
 from hotdata.models.update_embedding_provider_request import UpdateEmbeddingProviderRequest as UpdateEmbeddingProviderRequest
 from hotdata.models.update_embedding_provider_response import UpdateEmbeddingProviderResponse as UpdateEmbeddingProviderResponse
-from hotdata.models.update_sandbox_request import UpdateSandboxRequest as UpdateSandboxRequest
 from hotdata.models.update_saved_query_request import UpdateSavedQueryRequest as UpdateSavedQueryRequest
 from hotdata.models.update_secret_request import UpdateSecretRequest as UpdateSecretRequest
 from hotdata.models.update_secret_response import UpdateSecretResponse as UpdateSecretResponse
@@ -358,3 +348,11 @@ from hotdata.models.url_dataset_source import UrlDatasetSource as UrlDatasetSour
 from hotdata.models.workspace_detail import WorkspaceDetail as WorkspaceDetail
 from hotdata.models.workspace_list_item import WorkspaceListItem as WorkspaceListItem
 
+
+# --- hand-applied: prefer the enhanced clients over the generated ones
+# (re-applied by scripts/patch_query_exports.py after regeneration).
+# hotdata.query.QueryApi adds 429 retry + truncation auto-follow;
+# hotdata.arrow.ResultsApi adds Arrow IPC result fetch. The raw generated
+# classes remain importable from hotdata.api.query_api / hotdata.api.results_api.
+from hotdata.query import QueryApi as QueryApi  # noqa: E402,F811
+from hotdata.arrow import ResultsApi as ResultsApi  # noqa: E402,F811

hotdata-0.4.1/hotdata/_retry.py

@@ -0,0 +1,112 @@
+"""Transparent retry of pre-response connection resets (#118).
+
+A pooled keep-alive connection can be reused after an intermediary (load
+balancer / reverse proxy) has already dropped it for exceeding its idle
+timeout. The client is not notified, so the next request that reuses that
+socket fails immediately with::
+
+    urllib3.exceptions.ProtocolError:
+        ('Connection aborted.', ConnectionResetError(54, 'Connection reset by peer'))
+
+urllib3 classifies *every* :class:`~urllib3.exceptions.ProtocolError` as a
+*read* error (see ``Retry._is_read_error``) — it conservatively assumes the
+server may have begun processing the request. Read retries are gated by
+``allowed_methods``, which does not include ``POST``, so a ``POST`` that hits a
+dead pooled connection is re-raised to the caller instead of being retried.
+
+But a reset that happens *before any response bytes arrive* means the request
+never reached the server — the connection was already gone when urllib3 tried
+to send. That is safe to retry on **any** method, ``POST`` included, because the
+server did no work and a retry cannot double-execute.
+
+:class:`ConnectionResetRetry` reclassifies exactly that case — a
+``ProtocolError`` whose underlying cause is a connection-level ``OSError`` — as
+a *connection* error. urllib3's ``Retry.increment`` handles connection errors
+before read errors and without the ``allowed_methods`` gate, so the reset is
+retried on a fresh connection regardless of method. Read **timeouts**
+(:class:`~urllib3.exceptions.ReadTimeoutError`) and status retries are left
+untouched and stay idempotent-only, so a ``POST`` that may have reached the
+server is never blindly replayed.
+"""
+
+from __future__ import annotations
+
+from urllib3.exceptions import ProtocolError, ProxyError
+from urllib3.util.retry import Retry
+
+# Bounded attempts for the transparent connection-reset retry. Stale-pool resets
+# clear on the first fresh connection, so a small ceiling is plenty; it also
+# bounds the blast radius if a host is genuinely refusing connections.
+DEFAULT_TOTAL_RETRIES = 3
+
+# A small exponential backoff between attempts. The first retry on a fresh
+# connection almost always succeeds, so the delay stays sub-second; it exists
+# only to avoid hammering a host that is briefly flapping.
+DEFAULT_BACKOFF_FACTOR = 0.1
+
+
+def _is_pre_response_connection_reset(error: BaseException) -> bool:
+    """True for a connection reset/abort that occurred before any response.
+
+    urllib3 wraps a low-level socket failure raised while sending the request as
+    ``ProtocolError("Connection aborted.", <cause>)``, where ``<cause>`` is the
+    originating :class:`OSError` (``ConnectionResetError``,
+    ``ConnectionAbortedError``, ``BrokenPipeError``, …). Those builtin
+    connection errors all subclass :class:`ConnectionError`, so the cause's type
+    is a precise, message-independent signal that the failure was at the socket
+    layer before a response existed — distinct from a read **timeout**, which
+    urllib3 raises as a ``ReadTimeoutError`` (not a ``ProtocolError``) and which
+    we deliberately leave method-gated.
+    """
+    if isinstance(error, ProxyError):
+        error = error.original_error
+    if not isinstance(error, ProtocolError):
+        return False
+    cause = error.args[1] if len(error.args) > 1 else None
+    return isinstance(cause, ConnectionError)
+
+
+class ConnectionResetRetry(Retry):
+    """A :class:`urllib3.util.retry.Retry` that retries pre-response connection
+    resets on any HTTP method, while leaving read/status retries idempotent-only.
+
+    Behaves exactly like ``Retry`` except a connection reset/abort that happened
+    before any response bytes were received (see
+    :func:`_is_pre_response_connection_reset`) is treated as a *connection*
+    error rather than a *read* error. urllib3's ``increment`` retries connection
+    errors without consulting ``allowed_methods``, so the reset is retried on a
+    fresh connection for ``POST`` too — safe because the server did no work.
+    """
+
+    def _is_connection_error(self, err: Exception) -> bool:
+        if super()._is_connection_error(err):
+            return True
+        return _is_pre_response_connection_reset(err)
+
+
+def default_retry() -> ConnectionResetRetry:
+    """The SDK's default retry policy.
+
+    Matches urllib3's defaults (idempotent-only read/status retries, a bounded
+    total, no retry on response status codes) and adds transparent retry of
+    pre-response connection resets on every method. ``Configuration`` installs
+    this when the caller does not supply their own ``retries``.
+    """
+    return ConnectionResetRetry(
+        total=DEFAULT_TOTAL_RETRIES,
+        backoff_factor=DEFAULT_BACKOFF_FACTOR,
+        # Don't retry on response status codes by default: a status code means
+        # the request reached the server, and 429 admission-shedding already has
+        # dedicated handling in hotdata.query. Connection-reset retry is purely a
+        # transport-layer concern.
+        status=0,
+        raise_on_status=False,
+    )
+
+
+__all__ = [
+    "ConnectionResetRetry",
+    "DEFAULT_BACKOFF_FACTOR",
+    "DEFAULT_TOTAL_RETRIES",
+    "default_retry",
+]

{hotdata-0.3.1 → hotdata-0.4.1}/hotdata/api/__init__.py

@@ -14,7 +14,6 @@ from hotdata.api.query_api import QueryApi
 from hotdata.api.query_runs_api import QueryRunsApi
 from hotdata.api.refresh_api import RefreshApi
 from hotdata.api.results_api import ResultsApi
-from hotdata.api.sandboxes_api import SandboxesApi
 from hotdata.api.saved_queries_api import SavedQueriesApi
 from hotdata.api.secrets_api import SecretsApi
 from hotdata.api.uploads_api import UploadsApi

{hotdata-0.3.1 → hotdata-0.4.1}/hotdata/api/connections_api.py

@@ -69,7 +69,7 @@ class ConnectionsApi:
     ) -> ManagedSchemaResponse:
         """Add managed schema
 
-        Declare a new schema (and optionally its tables) on an existing managed catalog after creation. The schema is added to the connection's declaration; declared tables can then be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalised to lowercase.
+        Declare a new schema (and optionally its tables) on an existing managed catalog after creation. The schema is added to the connection's declaration; declared tables can then be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalized to lowercase.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -143,7 +143,7 @@ class ConnectionsApi:
     ) -> ApiResponse[ManagedSchemaResponse]:
         """Add managed schema
 
-        Declare a new schema (and optionally its tables) on an existing managed catalog after creation. The schema is added to the connection's declaration; declared tables can then be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalised to lowercase.
+        Declare a new schema (and optionally its tables) on an existing managed catalog after creation. The schema is added to the connection's declaration; declared tables can then be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalized to lowercase.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -217,7 +217,7 @@ class ConnectionsApi:
     ) -> RESTResponseType:
         """Add managed schema
 
-        Declare a new schema (and optionally its tables) on an existing managed catalog after creation. The schema is added to the connection's declaration; declared tables can then be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalised to lowercase.
+        Declare a new schema (and optionally its tables) on an existing managed catalog after creation. The schema is added to the connection's declaration; declared tables can then be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalized to lowercase.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -369,7 +369,7 @@ class ConnectionsApi:
     ) -> ManagedTableResponse:
         """Add managed table
 
-        Declare a new table on an existing schema of a managed catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalised to lowercase.
+        Declare a new table on an existing schema of a managed catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalized to lowercase.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -447,7 +447,7 @@ class ConnectionsApi:
     ) -> ApiResponse[ManagedTableResponse]:
         """Add managed table
 
-        Declare a new table on an existing schema of a managed catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalised to lowercase.
+        Declare a new table on an existing schema of a managed catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalized to lowercase.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -525,7 +525,7 @@ class ConnectionsApi:
     ) -> RESTResponseType:
         """Add managed table
 
-        Declare a new table on an existing schema of a managed catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalised to lowercase.
+        Declare a new table on an existing schema of a managed catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint. Only valid against connections whose source type is `managed`. Identifiers are normalized to lowercase.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -1497,7 +1497,7 @@ class ConnectionsApi:
     ) -> None:
         """Delete managed table
 
-        Delete a single managed-catalog table. The catalog row is removed and the backing parquet file (if any) is scheduled for deletion. Only valid against connections whose source type is `managed`.
+        Delete a single managed-catalog table. The table and its data are removed. Only valid against connections whose source type is `managed`.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -1574,7 +1574,7 @@ class ConnectionsApi:
     ) -> ApiResponse[None]:
         """Delete managed table
 
-        Delete a single managed-catalog table. The catalog row is removed and the backing parquet file (if any) is scheduled for deletion. Only valid against connections whose source type is `managed`.
+        Delete a single managed-catalog table. The table and its data are removed. Only valid against connections whose source type is `managed`.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -1651,7 +1651,7 @@ class ConnectionsApi:
     ) -> RESTResponseType:
         """Delete managed table
 
-        Delete a single managed-catalog table. The catalog row is removed and the backing parquet file (if any) is scheduled for deletion. Only valid against connections whose source type is `managed`.
+        Delete a single managed-catalog table. The table and its data are removed. Only valid against connections whose source type is `managed`.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -2603,7 +2603,7 @@ class ConnectionsApi:
     ) -> LoadManagedTableResponse:
         """Load managed table from upload
 
-        Publish a previously-uploaded parquet file as the new generation of a managed table. The upload must reference a parquet file (verified by magic bytes). Only `mode = \"replace\"` is supported. Concurrent loads against the same upload return 409.
+        Publish a previously-uploaded parquet file as the new contents of a managed table. The upload must reference a parquet file. Only `mode = \"replace\"` is supported. Concurrent loads against the same upload return 409.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -2685,7 +2685,7 @@ class ConnectionsApi:
     ) -> ApiResponse[LoadManagedTableResponse]:
         """Load managed table from upload
 
-        Publish a previously-uploaded parquet file as the new generation of a managed table. The upload must reference a parquet file (verified by magic bytes). Only `mode = \"replace\"` is supported. Concurrent loads against the same upload return 409.
+        Publish a previously-uploaded parquet file as the new contents of a managed table. The upload must reference a parquet file. Only `mode = \"replace\"` is supported. Concurrent loads against the same upload return 409.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str
@@ -2767,7 +2767,7 @@ class ConnectionsApi:
     ) -> RESTResponseType:
         """Load managed table from upload
 
-        Publish a previously-uploaded parquet file as the new generation of a managed table. The upload must reference a parquet file (verified by magic bytes). Only `mode = \"replace\"` is supported. Concurrent loads against the same upload return 409.
+        Publish a previously-uploaded parquet file as the new contents of a managed table. The upload must reference a parquet file. Only `mode = \"replace\"` is supported. Concurrent loads against the same upload return 409.
 
         :param connection_id: Connection ID (required)
         :type connection_id: str

{hotdata-0.3.1 → hotdata-0.4.1}/hotdata/api/databases_api.py

@@ -66,7 +66,7 @@ class DatabasesApi:
     ) -> ManagedSchemaResponse:
         """Add schema to database default catalog
 
-        Declare a new schema (and optionally its tables) on the database's auto-created default catalog after creation. The schema becomes reachable inside the database scope (e.g. `default.<schema>.<table>` and `information_schema.schemata`) without the caller addressing the internal default connection directly. Identifiers are normalised to lowercase.
+        Declare a new schema (and optionally its tables) on the database's auto-created default catalog after creation. The schema becomes reachable inside the database scope (e.g. `default.<schema>.<table>` and `information_schema.schemata`) without the caller addressing the internal default connection directly. Identifiers are normalized to lowercase.
 
         :param database_id: Database ID (required)
         :type database_id: str
@@ -140,7 +140,7 @@ class DatabasesApi:
     ) -> ApiResponse[ManagedSchemaResponse]:
         """Add schema to database default catalog
 
-        Declare a new schema (and optionally its tables) on the database's auto-created default catalog after creation. The schema becomes reachable inside the database scope (e.g. `default.<schema>.<table>` and `information_schema.schemata`) without the caller addressing the internal default connection directly. Identifiers are normalised to lowercase.
+        Declare a new schema (and optionally its tables) on the database's auto-created default catalog after creation. The schema becomes reachable inside the database scope (e.g. `default.<schema>.<table>` and `information_schema.schemata`) without the caller addressing the internal default connection directly. Identifiers are normalized to lowercase.
 
         :param database_id: Database ID (required)
         :type database_id: str
@@ -214,7 +214,7 @@ class DatabasesApi:
     ) -> RESTResponseType:
         """Add schema to database default catalog
 
-        Declare a new schema (and optionally its tables) on the database's auto-created default catalog after creation. The schema becomes reachable inside the database scope (e.g. `default.<schema>.<table>` and `information_schema.schemata`) without the caller addressing the internal default connection directly. Identifiers are normalised to lowercase.
+        Declare a new schema (and optionally its tables) on the database's auto-created default catalog after creation. The schema becomes reachable inside the database scope (e.g. `default.<schema>.<table>` and `information_schema.schemata`) without the caller addressing the internal default connection directly. Identifiers are normalized to lowercase.
 
         :param database_id: Database ID (required)
         :type database_id: str
@@ -366,7 +366,7 @@ class DatabasesApi:
     ) -> ManagedTableResponse:
         """Add table to database default catalog
 
-        Declare a new table on an existing schema of the database's default catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint targeting the default connection. Identifiers are normalised to lowercase.
+        Declare a new table on an existing schema of the database's default catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint targeting the default connection. Identifiers are normalized to lowercase.
 
         :param database_id: Database ID (required)
         :type database_id: str
@@ -444,7 +444,7 @@ class DatabasesApi:
     ) -> ApiResponse[ManagedTableResponse]:
         """Add table to database default catalog
 
-        Declare a new table on an existing schema of the database's default catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint targeting the default connection. Identifiers are normalised to lowercase.
+        Declare a new table on an existing schema of the database's default catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint targeting the default connection. Identifiers are normalized to lowercase.
 
         :param database_id: Database ID (required)
         :type database_id: str
@@ -522,7 +522,7 @@ class DatabasesApi:
     ) -> RESTResponseType:
         """Add table to database default catalog
 
-        Declare a new table on an existing schema of the database's default catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint targeting the default connection. Identifiers are normalised to lowercase.
+        Declare a new table on an existing schema of the database's default catalog after creation. The table is added empty (declared-but-unloaded) and can be populated via the managed-table load endpoint targeting the default connection. Identifiers are normalized to lowercase.
 
         :param database_id: Database ID (required)
         :type database_id: str
@@ -977,7 +977,7 @@ class DatabasesApi:
     ) -> CreateDatabaseResponse:
         """Create database
 
-        Create a new database (a metadata-only grouping). A managed default catalog is auto-created and addressable inside the database as `default` (or the optional `default_catalog` name), with a `main` schema pre-declared so `default.main.<table>` works out of the box. The optional `name` is a free-form display label and is not required to be unique. Optional `default_catalog` overrides the name the default catalog answers to; it must be a valid SQL identifier and may not collide with the `hotdata`, `datasets`, or `information_schema` system catalogs. Optional `schemas` declares additional schemas/tables on the default catalog at create time; declared tables can be loaded via the standard managed-tables-load endpoint targeting `default_connection_id`. Optional `expires_at` sets when the database expires — accepts either an RFC 3339 timestamp or a relative duration suffixed with `h` (hours), `m` (minutes), or `d` (days), e.g. `24h`, `48h`, `90m`, `7d`. When omitted, the database never expires. Expiry is best-effort: the database will not be deleted before `expires_at`, but cleanup may run later than the exact timestamp. Optional `storage_backend` selects the physical backend for the default catalog — `parquet` (default) or `ducklake` (requires `ducklake.metadata_pg_url` to be configured).
+        Create a new database (a metadata-only grouping). A managed default catalog is auto-created and addressable inside the database as `default` (or the optional `default_catalog` name), with a `main` schema pre-declared so `default.main.<table>` works out of the box. The optional `name` is a free-form display label and is not required to be unique. Optional `default_catalog` overrides the name the default catalog answers to; it must be a valid SQL identifier and may not collide with the `hotdata`, `datasets`, or `information_schema` system catalogs. Optional `schemas` declares additional schemas/tables on the default catalog at create time; declared tables can be loaded via the standard managed-tables-load endpoint targeting `default_connection_id`. Optional `expires_at` sets when the database expires — accepts either an RFC 3339 timestamp or a relative duration suffixed with `h` (hours), `m` (minutes), or `d` (days), e.g. `24h`, `48h`, `90m`, `7d`. When omitted, the database never expires. Expiry is best-effort: the database will not be deleted before `expires_at`, but cleanup may run later than the exact timestamp.
 
         :param create_database_request: (required)
         :type create_database_request: CreateDatabaseRequest
@@ -1046,7 +1046,7 @@ class DatabasesApi:
     ) -> ApiResponse[CreateDatabaseResponse]:
         """Create database
 
-        Create a new database (a metadata-only grouping). A managed default catalog is auto-created and addressable inside the database as `default` (or the optional `default_catalog` name), with a `main` schema pre-declared so `default.main.<table>` works out of the box. The optional `name` is a free-form display label and is not required to be unique. Optional `default_catalog` overrides the name the default catalog answers to; it must be a valid SQL identifier and may not collide with the `hotdata`, `datasets`, or `information_schema` system catalogs. Optional `schemas` declares additional schemas/tables on the default catalog at create time; declared tables can be loaded via the standard managed-tables-load endpoint targeting `default_connection_id`. Optional `expires_at` sets when the database expires — accepts either an RFC 3339 timestamp or a relative duration suffixed with `h` (hours), `m` (minutes), or `d` (days), e.g. `24h`, `48h`, `90m`, `7d`. When omitted, the database never expires. Expiry is best-effort: the database will not be deleted before `expires_at`, but cleanup may run later than the exact timestamp. Optional `storage_backend` selects the physical backend for the default catalog — `parquet` (default) or `ducklake` (requires `ducklake.metadata_pg_url` to be configured).
+        Create a new database (a metadata-only grouping). A managed default catalog is auto-created and addressable inside the database as `default` (or the optional `default_catalog` name), with a `main` schema pre-declared so `default.main.<table>` works out of the box. The optional `name` is a free-form display label and is not required to be unique. Optional `default_catalog` overrides the name the default catalog answers to; it must be a valid SQL identifier and may not collide with the `hotdata`, `datasets`, or `information_schema` system catalogs. Optional `schemas` declares additional schemas/tables on the default catalog at create time; declared tables can be loaded via the standard managed-tables-load endpoint targeting `default_connection_id`. Optional `expires_at` sets when the database expires — accepts either an RFC 3339 timestamp or a relative duration suffixed with `h` (hours), `m` (minutes), or `d` (days), e.g. `24h`, `48h`, `90m`, `7d`. When omitted, the database never expires. Expiry is best-effort: the database will not be deleted before `expires_at`, but cleanup may run later than the exact timestamp.
 
         :param create_database_request: (required)
         :type create_database_request: CreateDatabaseRequest
@@ -1115,7 +1115,7 @@ class DatabasesApi:
     ) -> RESTResponseType:
         """Create database
 
-        Create a new database (a metadata-only grouping). A managed default catalog is auto-created and addressable inside the database as `default` (or the optional `default_catalog` name), with a `main` schema pre-declared so `default.main.<table>` works out of the box. The optional `name` is a free-form display label and is not required to be unique. Optional `default_catalog` overrides the name the default catalog answers to; it must be a valid SQL identifier and may not collide with the `hotdata`, `datasets`, or `information_schema` system catalogs. Optional `schemas` declares additional schemas/tables on the default catalog at create time; declared tables can be loaded via the standard managed-tables-load endpoint targeting `default_connection_id`. Optional `expires_at` sets when the database expires — accepts either an RFC 3339 timestamp or a relative duration suffixed with `h` (hours), `m` (minutes), or `d` (days), e.g. `24h`, `48h`, `90m`, `7d`. When omitted, the database never expires. Expiry is best-effort: the database will not be deleted before `expires_at`, but cleanup may run later than the exact timestamp. Optional `storage_backend` selects the physical backend for the default catalog — `parquet` (default) or `ducklake` (requires `ducklake.metadata_pg_url` to be configured).
+        Create a new database (a metadata-only grouping). A managed default catalog is auto-created and addressable inside the database as `default` (or the optional `default_catalog` name), with a `main` schema pre-declared so `default.main.<table>` works out of the box. The optional `name` is a free-form display label and is not required to be unique. Optional `default_catalog` overrides the name the default catalog answers to; it must be a valid SQL identifier and may not collide with the `hotdata`, `datasets`, or `information_schema` system catalogs. Optional `schemas` declares additional schemas/tables on the default catalog at create time; declared tables can be loaded via the standard managed-tables-load endpoint targeting `default_connection_id`. Optional `expires_at` sets when the database expires — accepts either an RFC 3339 timestamp or a relative duration suffixed with `h` (hours), `m` (minutes), or `d` (days), e.g. `24h`, `48h`, `90m`, `7d`. When omitted, the database never expires. Expiry is best-effort: the database will not be deleted before `expires_at`, but cleanup may run later than the exact timestamp.
 
         :param create_database_request: (required)
         :type create_database_request: CreateDatabaseRequest