Skip to main content
The oleander CLI lets you manage Spark artifacts and jobs, run SQL queries against the lake, browse catalogs, register infrastructure, and launch a DuckDB terminal from the command line. Queries go through the query router, so the CLI picks the engine and machine size for you.

Installation

The install script puts a standalone oleander binary in ~/.oleander/bin and adds it to your PATH, so Node.js is not required. Re-run the script, or run oleander upgrade, to upgrade.

All install methods

The scripts, Scoop, and the standalone archives install a self-contained binary, so Node.js is only needed for the npm package.

Configuration

Authenticate with an API key from your oleander settings. Pass a profile name. In a terminal, the CLI prompts for the key and stores it in ~/.oleander/config.json. The first profile you configure becomes the current profile.
Outside a terminal, set OLEANDER_API_KEY or pipe the key on stdin:
Configure one profile per organization or API key. Run oleander configure without --profile to update the current profile’s key.
Set OLEANDER_PROFILE to use a profile for a whole shell session.

Output format

Commands that print results accept -o, --output <format>: table (the default), json, or csv. Commands that don’t print rows, such as query submit, take table or json.

Upgrade

Upgrade to the latest release:
Check whether an update is available without installing it:

Commands

General

Lake

Catalogs

Spark

Env

Queries

See Spark, Lake, Polars, Env, and Queries for detailed usage.