Rockset
Rockset is currently available as a destination connector for credential validation only. Data loading is still in development.
Setup
Before configuring the connector, you’ll need:
- A Rockset API key
- Your Rockset API endpoint (the base URL for the Rockset API in your region)
Authentication
This connector authenticates using a Rockset API key.
During credential validation, the connector makes a request to:
GET {endpoint}/v1/orgs/self
and sends the header:
Authorization: ApiKey <api_key>
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
endpoint | string | Yes | Rockset API base URL (for example, https://api.usw2a1.rockset.com). |
api_key | string | Yes | Rockset API key used to authenticate requests. |
Streams
This is a destination connector. It does not expose source streams.
Limitations
- Loading is not yet supported. Runs will fail at load time with an “in development” error even if credentials validate successfully.
Hashing and normalization
This destination connector does not currently expose field-level hashing.
Data contract
Rockset destination loading is still in development, so a stable, documented data contract (object mapping, upsert behavior, required identifiers, and supported data types) is not yet available.