Skip to content
HyperlakeHyperlake

Data and semantic commands

Query

Section titled “Query”
Terminal window
hyperlake catalog list --cluster CLUSTER_ID
hyperlake query schemas --cluster CLUSTER_ID --catalog CATALOG
hyperlake query tables --cluster CLUSTER_ID --catalog CATALOG --schema SCHEMA
hyperlake query run --cluster CLUSTER_ID --sql SQL [--catalog CATALOG] [--schema SCHEMA] [--json|--csv]

The query command is read-only at the Hyperlake boundary. Database-level permissions still apply, and a catalog may further restrict rows or mask columns.

Catalog grants

Section titled “Catalog grants”
Terminal window
hyperlake catalog grants list
hyperlake catalog grants status --cluster CLUSTER_ID
hyperlake catalog grants sync --cluster CLUSTER_ID
hyperlake catalog grants test --cluster CLUSTER_ID --sql SQL --as-member-email EMAIL

Grant creation and updates are administrative actions. Use the narrowest catalog, schema, table, operation, row-filter, and column-mask scope required by the policy.

Semantic access

Section titled “Semantic access”
Terminal window
hyperlake semantic_dataLake health
hyperlake semantic_dataLake dimensions --email EMAIL --model MODEL
hyperlake semantic_dataLake metrics --email EMAIL --model MODEL
hyperlake semantic_dataLake match --email EMAIL --question 'revenue by region'
hyperlake semantic_dataLake build-json --email EMAIL --question 'revenue by region'

Semantic commands help select a model and build a query request. They do not grant access by themselves. The final query remains subject to the target’s data policy.