Skip to content

docs(nested-columns): state the minimum CLI version and the not-unnested warning #1234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tatianainama wants to merge 1 commit into from
Closed

docs(nested-columns): state the minimum CLI version and the not-unnested warning #1234

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion semantic-layer/nested-and-repeated-columns.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,9 @@ models:

## Deploy and generate

Explores compile in the CLI during [`lightdash deploy`](/workflow/cli/deploy), and the CLI reads the nested-column setting from the Lightdash server. Before deploying, [update the Lightdash CLI](/workflow/cli/install#updating-the-lightdash-cli). If the CLI cannot reach the server or read the setting, it compiles with nested-column support disabled and silently drops repeated leaves from the Explore.
Explores compile in the CLI during [`lightdash deploy`](/workflow/cli/deploy), and the CLI reads the nested-column setting from the Lightdash server. Nested-column support needs Lightdash CLI 2.153.0 or later, so [update the Lightdash CLI](/workflow/cli/install#updating-the-lightdash-cli) before deploying. If the CLI cannot reach the server or read the setting, it prints a warning and compiles with nested-column support disabled.

When a model documents fields under a repeated column but they were not unnested, because the setting is off for your organization or the deploy came from an older CLI, the deploy output, the Explore and the [validation page](/workflow/validating-your-content) show a warning naming the model and the affected fields. Selecting one of those fields fails on BigQuery until you enable the setting or upgrade the CLI and deploy again.

On self-hosted deployments, add `unnest-repeated-columns` to `LIGHTDASH_ENABLE_FEATURE_FLAGS`; see [Feature flags](/self-host/customize-deployment/environment-variables#feature-flags).

Expand Down
Loading