cancel
Showing results for 
Search instead for 
Did you mean: 
Warehousing & Analytics
Engage in discussions on data warehousing, analytics, and BI solutions within the Databricks Community. Share insights, tips, and best practices for leveraging data for informed decision-making.
cancel
Showing results for 
Search instead for 
Did you mean: 

Truncated Data on Lakeview Dashboard

Akshay_Petkar
Contributor III

When we create a Lakeview dashboard, the visuals show truncated data. I want to create a dashboard using the entire dataset because the charts do not display the exact values needed for accurate analysis.

1 ACCEPTED SOLUTION

Accepted Solutions

raphaelblg
Databricks Employee
Databricks Employee

Hello @Akshay_Petkar ,

The FrontEnd (FE) rendering is a limit that determines what data we render on the FE that has been returned by the BackEnd (BE). Render all button allows you to render all the data on the FE that has been returned by the BE.

Render all is available in interactive use cases like the Notebook or the Notebook Dashboard. Jobs runs are not interactive by definition, so there is no render all. A job runs, completes and has results. An individual run can’t be updated.

Every visualization on a Notebook that is run via a Job will either use the results from the table tab (FE aggregation w/ no cost to the customer) or it will run a separate command over all data (BE aggregation w/ a cost to the customer).

We decide between FE aggregation and BE aggregation based on how the Notebook asset was last run. If you would like this job to always BE aggregate the visualization so that it runs over all data, then you should make sure that Notebook that the job is based on does the same.

 

Best regards,

Raphael Balogo
Sr. Technical Solutions Engineer
Databricks

View solution in original post

2 REPLIES 2

raphaelblg
Databricks Employee
Databricks Employee

Hello @Akshay_Petkar ,

The FrontEnd (FE) rendering is a limit that determines what data we render on the FE that has been returned by the BackEnd (BE). Render all button allows you to render all the data on the FE that has been returned by the BE.

Render all is available in interactive use cases like the Notebook or the Notebook Dashboard. Jobs runs are not interactive by definition, so there is no render all. A job runs, completes and has results. An individual run can’t be updated.

Every visualization on a Notebook that is run via a Job will either use the results from the table tab (FE aggregation w/ no cost to the customer) or it will run a separate command over all data (BE aggregation w/ a cost to the customer).

We decide between FE aggregation and BE aggregation based on how the Notebook asset was last run. If you would like this job to always BE aggregate the visualization so that it runs over all data, then you should make sure that Notebook that the job is based on does the same.

 

Best regards,

Raphael Balogo
Sr. Technical Solutions Engineer
Databricks

Hello @Raphael Balogo

Thank you for the detailed explanation. I am referring to the SQL Lakeview Dashboard, where we select visualizations on the canvas and add fields to them. I would like to know if there is a way to display the entire dataset in a visualization on the Lakeview Dashboard, or if the data is always truncated.

Thank you,
Akshay Petkar.


 

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now