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
Three things can be done to improve the clarity here:
Data source names should refer to the content of the data rather than (or in addition to) the name of the datastore (e.g. perhaps "Desktop User Telemetry (Athena)" instead of simply "Athena")
Link to a set of examples using this data source. These could be queries living in Redash that are created and reviewed by "trusted authorities". Some such examples exist within Redash already but they are very difficult to discover.
The text was updated successfully, but these errors were encountered:
This all points to a bigger issue, which is that we need to both store and show more complete / better metadata on the data sources. We could tackle this piecemeal, but I think it makes more sense to be thought of as a bigger, well thought out initiative. We're currently handling both react migration and extensions stuff, this will go in the queue for one of the next bigger things we work on.
Three things can be done to improve the clarity here:
Data source names should refer to the content of the data rather than (or in addition to) the name of the datastore (e.g. perhaps "Desktop User Telemetry (Athena)" instead of simply "Athena")
Some documentation already exists that can simply be linked inside of the Redash UI to show what the data schema for a given data source looks like. E.g. https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/main-ping.html
Link to a set of examples using this data source. These could be queries living in Redash that are created and reviewed by "trusted authorities". Some such examples exist within Redash already but they are very difficult to discover.
The text was updated successfully, but these errors were encountered: