On this page
Kater CLI Present and share chart
kater chart read
Shows one saved chart: its title, its spec, its SQL and its revision.
Read a chart before you change it, because each change needs its revision. It changes nothing.
Examples
# Show the spend_mix chartkater chart read --request-file spend_mix.json# Keep the chart in a file, to make a change request from it with jqkater chart read --request-file spend_mix.json --json > spend_mix_read.jsonArguments
Options
It also takes the global options --json, --kater-root, --scope and --help.
The request
| Field | What it holds |
|---|---|
chart | The chart: its name, and the full path of its workspace under namespace. |
{"chart": {"name": "spend_mix", "namespace": {"path": "connections/snowflake_prod_connection/workspaces/ad_reporting"}}}What it shows
The answer holds the chart in definition:
| Field | What it holds |
|---|---|
title | The title the chart shows: its label, or what it shows, such as “Clicks by Platform”. |
path | The chart’s file, such as connections/snowflake_prod_connection/workspaces/ad_reporting/charts/spend_mix.sql. |
revision | The chart’s revision. A change request gives it as expected_revision. |
spec | The chart: its name in relation, its query in source, its kind, its encodings and its presentation. |
sql | The SQL that selects the query’s columns for the chart. |
plan | The same selection as sql, in parts: the columns, the conditions, the order and the limit. |
diagnostics | The problems Kater found in the chart. |