Jinja Template

[Meena0155]

I am having issues while writing superset datasets that use Jinja template.

I can run the query successfully using sql lab. However when I save the query as a dataset and use it in a chart, the jinja template is disappearing.

This is the query I used

`SELECT
*
from my_table
where
1=1
{% if filter_values('Date')|length %}
and
event_time<=TIMESTAMP'{{filter_values('Date')[0]}}' and event_time>= date_add('day',-14,TIMESTAMP'{{filter_values('Date')[0]}}')

{% endif %}
`
however when I view query in the chart it just show SELECT
*
from my_table
where
1=1 as virtual table.

Please help.

The Template parameter is enabled in the superset config file

[dosubot[bot]]

Hey there, @Meena0155! I'm here to help you with any bugs, questions, or contributions you have in mind. Let's work together to solve this issue!

The issue you're experiencing with the Jinja template disappearing when saving a query as a dataset in Superset is due to the templateParams being modified before saving. Specifically, the _filters entry used for testing filters in SQL Lab is removed and not stored with the dataset, causing the Jinja template to not persist ^[1].

A similar issue was discussed in a closed issue where it was identified as a duplicate of another issue. You might want to check the conversation in this thread for potential solutions ^[2].

To continue talking to Dosu, mention @dosu.

[dosubot[bot]]

If filter_values works in SQL Lab but not in charts or dashboards, it might be due to how template parameters are handled when transitioning from SQL Lab to other components. In Superset, templateParams are used to manage these parameters, and they might not be correctly passed or interpreted when moving to charts or dashboards ^[1][2].

Here are a few things to check:

1. Template Parameters: Ensure that the template parameters are correctly defined and passed when creating the chart or dashboard. They should be available in the query using Jinja templating syntax.

2. Jinja Context: Verify that the Jinja context in jinja_context.py is correctly set up to handle filter_values in the context of charts and dashboards ^[3].

3. Chart Metadata: Check if the chart metadata includes the necessary URL parameters or context that might be required for the Jinja template to function correctly.

If these aspects are correctly configured and the issue persists, it might be worth reviewing the specific implementation of filter_values in the Jinja context to ensure it aligns with your use case.

To continue talking to Dosu, mention @dosu.

[Meena0155]

Thank you.. Is it possible to use use jinja templates without jinja_context.py file? @dosu

[dosubot[bot]]

Yes, it's possible to use Jinja templates in Superset without a jinja_context.py file. Superset uses a BaseTemplateProcessor class to handle Jinja templating. This class sets up a Jinja environment and processes SQL templates. Additional context can be added using the context_addons function, which pulls from the application configuration ^[1].

To continue talking to Dosu, mention @dosu.

[Meena0155]

@dosu where can I find BaseTemplateProcessor class? Our superset installation does not have jinja_context.py but I can use jinja template in sql lab but not in dashboard. Is it possible to assign the ticket to any support engineer?

[dosubot[bot]]

The BaseTemplateProcessor class is located in the superset/jinja_context.py file. If your installation doesn't have this file, you can still use Jinja templates by leveraging the context_addons function, which allows you to add custom context from your app configuration. This is done by setting JINJA_CONTEXT_ADDONS in your application settings ^[1].

Regarding assigning tickets, I'm unable to assign tasks or tickets to support engineers. However, you can follow the guidance provided to troubleshoot and resolve the issue.

This is a tough nut to crack, could really use your help on this, @rusackas.

To continue talking to Dosu, mention @dosu.

[smokeriu]

Have you solved this problem? I encountered a similar issue, and my version is 4.1.1.

Thanks