Skip to main content

Overview

Installing the CLI

If you are on Linux or macOS, please run the following command to install the CLI:
The script automatically detects your platform, downloads and installs the latest version of CLI, If you are on Windows use WSL. After installing the CLI, run:
This command performs the initial setup by creating the required local directories and downloading the FlareDB binary and Apache Beam worker JAR. The initialization only needs to be completed once. After that, you can use the flare up and flare down commands to manage the instance. See the usage guide to learn how to submit pipeline job to the FlareDB instance

Job logs

A JOB-ID is generated automatically for each submitted job. Use it to view logs for a specific job, or stream the most recent logs when you do not provide an ID. Logs are followed continuously by default.
The JOB-ID is logged during job submission via the runner SDK.

Versions and Updates

The version command prints the installed flare CLI , FlareDB, and beam-java-worker versions, then checks for newer releases and reports how to upgrade each one.
If you see new available versions, use update command to download the latest FlareDB engine and Beam Java worker. Pass --db or --java-worker to update a specfic component. Older versions left in the bin directory are removed once the new one is dowloaded. if no flags are provided it updates both the db and worker to their latest versions
While updating, stop any active FlareDB instance and run the updates.

Updating the CLI

Run the installer script again to upgrade the flare-cli. It checks for a newer release and upgrades automatically, or if there are no new updates it reports that you are already on the latest version.
  • Quickstart - install the CLI and run a complete local WordCount example.
  • SQL shell - query and manage FlareDB tables from the interactive shell.
  • Run a Beam pipeline - submit your own pipeline jobs to a running instance.
Last modified on October 11, 2026