Connect to Zetaris
Get access first. You need the website URL, your account and query permission. Keep credentials private.
SQL Editor
Sign in and open the SQL Editor. This is the recommended beginner route and needs no additional client tools.
Run your first SQL commands to confirm execution and query the supplied samples. Run one complete statement at a time and wait for the result.
Coding assistants
This is an optional alternative to SQL Editor.
Configure client setup, then follow Cursor, Codex, or Claude Code for the starter prompt. JDBC needs Java, the matching driver JAR, endpoint and account.
Use the Zetaris driver; don't substitute a Hive/Spark driver or start a local Spark session. Direct REST uses an API key and the platform's OpenAPI specification; follow your assistant's guide.
HTTP helpers
This is another optional route. You need Python or Deno, the UI URL, numeric organisation ID, and an account or token.
Follow client scripts for .env.local, authentication and the connection check. The helpers use UI proxy routes; the raw API URL is not a substitute.
Next step
Once connected, run your first SQL commands. Use the full reference later for additional commands and their prerequisites.
Start with your coding assistant
Open this repository in your assistant, choose a connection and review the prompt before sending it.
Use the getting-started repository at https://github.com/zetaris/getting-started/tree/44668b267ad7ee0fae25ce7588e9620121d47cae as the workspace. If it is not checked out, help me clone and open it first. Read docs/connections/client-setup.md for setup. Keep credentials in .env.local, never in this prompt or a report.
Read AGENTS.md and follow it. Run python3 scripts/preflight.py --jdbc and show
me the result. Report JDBC and REST checks separately. Stop on JDBC failures and report
what is missing. REST failures alone do not block JDBC. If the driver JAR path is not set, ask me
for it. Once readiness checks pass, connect over JDBC to the instance
configured in .env.local and confirm with SELECT 1 and SHOW LIGHTNING DATABASES.
If a local port check returns `Operation not permitted`, retry the same
read-only check with approved network access before reporting the endpoint as
closed. Distinguish missing Python runner dependencies (`.venv` or
`jaydebeapi`) from direct Java JDBC readiness; do not install dependencies
without asking.
Goal: verify SQL execution, inspect the supplied NY_TAXI and TPCDS_DB tables, then run a sample SELECT with LIMIT 5. Do not create objects.
Dry-run before creating anything and wait for my go-ahead.
Requires the desktop app. If it doesn't open, copy the prompt into your assistant. Configure .env.local first; JDBC also needs the matching driver JAR.