Flight SQL Data Connector

Connect to any Flight SQL compatible server (e.g. Influx 3.0, CnosDB, other Spice runtimes!) as a connector for federated SQL queries.

params

• endpoint: The Apache Flight endpoint used to connect to the Flight SQL server.

Auth

Username and password credentials can be specified to connect to the Flight SQL server:

• username (optional): The username to use in the underlying Apache flight Handshake Request to authenticate to the server (see reference).
• password (optional): The password to use in the underlying Apache flight Handshake Request to authenticate to the server (see reference).

By default Flight SQL connector will look for a secret named flightsql with keys username and password.

Check Secrets Stores for more details.

Env

SPICE_SECRET_FLIGHTSQL_USERNAME=<flight_username> \
SPICE_SECRET_FLIGHTSQL_PASSWORD=<flight_password> \
spice run

spicepod.yaml

version: v1beta1
kind: Spicepod
name: spice-app

secrets:
  store: env

# <...>

Learn more about Env Secret Store.

Kubernetes

kubectl create secret generic flightsql \
  --from-literal=username='<flight_username>' \
  --from-literal=password='<flight_password>'

spicepod.yaml

version: v1beta1
kind: Spicepod
name: spice-app

secrets:
  store: kubernetes

# <...>

Learn more about Kubernetes Secret Store.

Keyring

Add new keychain entry (macOS), with user and password in JSON string

security add-generic-password -l "Flight SQL Secret" \
-a spiced -s spice_secret_flightsql \
-w $(echo -n '{"username": "<flight_username>", "password": "<flight_password>"}')

spicepod.yaml

version: v1beta1
kind: Spicepod
name: spice-app

secrets:
  store: keyring

# <...>

Learn more about Keyring Secret Store.

Example

- from: flightsql:my_catalog.good_schemas.cool_dataset
  name: cool_dataset
  params:
    endpoint: http://127.0.0.1:50051