You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 3, 2024. It is now read-only.
There is a limited view of the data that is actually sent to the UI. I have found myself wondering some of the statistics about the data while building queries using the widget.
A simple example is the number of rows in the table. A more complicated example may be some statistical analysis of numeric columns, for example standard deviation and distribution.
It would be nice to have some common information like this baked in to the widget so I don't have to keep writing little annoying code cells to see these things.
These computations may be expensive, so we could have buttons to retrieve them so they don't keep getting automatically run. For each column, there could be a "stats" button in the column header that opens up some popup/panel for that column. There could also be a "Stats" card in the list of sidebar cards. It could initially just contain a button "compute stats" that when clicked runs some computations and returns the stats to populate the card contents. Either of these examples could have a refresh button, and we may need to cache the stats for each query level.
There is a limited view of the data that is actually sent to the UI. I have found myself wondering some of the statistics about the data while building queries using the widget.
A simple example is the number of rows in the table. A more complicated example may be some statistical analysis of numeric columns, for example standard deviation and distribution.
It would be nice to have some common information like this baked in to the widget so I don't have to keep writing little annoying code cells to see these things.
These computations may be expensive, so we could have buttons to retrieve them so they don't keep getting automatically run. For each column, there could be a "stats" button in the column header that opens up some popup/panel for that column. There could also be a "Stats" card in the list of sidebar cards. It could initially just contain a button "compute stats" that when clicked runs some computations and returns the stats to populate the card contents. Either of these examples could have a refresh button, and we may need to cache the stats for each query level.