Skip to content
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

Jump to bottom

docs: fix sql templating typos #18955

Merged
merged 3 commits into from
Feb 28, 2022
Merged

docs: fix sql templating typos #18955

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
df11315
Fix minor typo
garyng Feb 27, 2022
819729e
Spacing
garyng Feb 27, 2022
660764b
Fix casing
garyng Feb 27, 2022
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
14 changes: 7 additions & 7 deletions docs/docs/installation/sql-templating.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ In this section, we'll walkthrough the pre-defined Jinja macros in Superset.

The `{{ current_username() }}` macro returns the username of the currently logged in user.

If you have caching enabled in your Superset configuration, then by defaul the the `username` value will be used
If you have caching enabled in your Superset configuration, then by default the the `username` value will be used
by Superset when calculating the cache key. A cache key is a unique identifer that determines if there's a
cache hit in the future and Superset can retrieve cached data.

Expand All @@ -132,7 +132,7 @@ cache key by adding the following parameter to your Jinja code:

**Current User ID**

The `{{ current_user_id()}}` macro returns the user_id of the currently logged in user.
The `{{ current_user_id() }}` macro returns the user_id of the currently logged in user.

If you have caching enabled in your Superset configuration, then by defaul the the `user_id` value will be used
by Superset when calculating the cache key. A cache key is a unique identifer that determines if there's a
Expand Down Expand Up @@ -197,8 +197,8 @@ You can retrieve the value for a specific filter as a list using `{{ filter_valu

This is useful if:

- you want to use a filter component to filter a query where the name of filter component column doesn't match the one in the select statement
- you want to have the ability for filter inside the main query for performance purposes
- You want to use a filter component to filter a query where the name of filter component column doesn't match the one in the select statement
- You want to have the ability for filter inside the main query for performance purposes

Here's a concrete example:

Expand All @@ -218,9 +218,9 @@ returns the operator specified in the Explore UI.

This is useful if:

- you want to handle more than the IN operator in your SQL clause
- you want to handle generating custom SQL conditions for a filter
- you want to have the ability to filter inside the main query for speed purposes
- You want to handle more than the IN operator in your SQL clause
- You want to handle generating custom SQL conditions for a filter
- You want to have the ability to filter inside the main query for speed purposes

Here's a concrete example:

Expand Down