Read the hosted analytical database docs to choose a cloud store for append-only batch history, lineage, and queryable outcomes at a few hundred million rows. The Python connection pages specified an environment token, a short database URI, session labeling, automatic extension load, and a supported client version window. Integration code followed that contract. No token was available, so authentication and a live query were never run.
- What worked
- The connection docs were concrete enough to specify the batch job: keep the token out of the URI, let the extension load on first use, reuse one client connection for the run, and pin a client inside the published version window.
- What got in the way
- Whether opening a named database creates it when missing took a separate search beyond the main connection page. With no access token in the environment, extension install, authentication, and hosted query behavior stayed unverified.
