EBoisseauSierra opened a new issue #14548:
URL: https://github.com/apache/superset/issues/14548
## Issue
As a new user to Superset, I have been confused by the default behaviour in
the Explore mode.
## Suggestions
1. _Time_ section
* issue: By default, only “last week”'s data are used. This filter is
applied silently: a new user might not immediately notice that “Time range:
Last week” means some data are not considered. And this can be quite puzzling
if one deals with forecast (i.e. future) data, as the user then gets a “No
Results” error.
* suggestion: Don't apply filters by default — or if so, let the user know
about them.
2. _Query/Metrics_ section
* issue: By default, `COUNT(*)` is selected (as the only pre-defined
“metric”). This feels counter-intuitive to me, as I mostly know what chart I
want to build, and it's almost never using `COUNT(*)` as main KPI. I then have
the surprise/frustration of having a chart populated with something different
from what I have in mind.
* suggestion: Could we prevent the chart from “trying to be smart”, and:
* have “metrics” non pre-filled,
* don't run the query straight away, but wait for the user to first
specify the chart/dashboard and them to click “run”.
The “Run” button could be greyed out/disabled as long as mandatory fields
for the chart aren't populated yet.
3. _Query/Metrics_ section
* issue: I don't want to be forced to chose an aggregate. Indeed, the data
I query are sometimes already “aggregated” (say I want to plot temperature over
time by location and I have only one reading per location and per hour (at the
`*:00.000` timestamp)), and in that case “aggregating” seems counter-intuitive
(even if, I agree, `SUM`, `AVG`, `MIN`, and `MAX` would return the same value).
Yet when adding a Metric / Simple, the “Save” button is greyed out after I
select a column, until I choose an aggregate.
* suggestion: Allow users to _not_ select any aggregate, and fail if
multiple record for the same index are returned.
4. _Dataset / Columns_ panel
* issue: While most data types have an “icon” next to the column name (str
￫ `ABC`, timestamp ￫ :clock9: , int ￫ `#`), PostgreSQL “Double Precision” don't.
* suggestion: Define an icon for it (same as float if exist, or something
like `#.##`)?
5. Explore a whole dataset
* issue: First go to the Data/Dataset menu. Then when clicking on a given
dataset, the Explore panel opens. Yet the default query is basically `SELECT
COUNT(*) WHERE (timestamp ≥ now() - 7 AND timestamp < now())`, in the Table
chart's “Aggregate” query mode. As detailed above, this can cause some
confusion.
* suggestion: Set default query to `SELECT *` (possibly appending a `LIMIT
100`) and set the table in “Raw records” mode. Indeed, when I click on a
dataset, I expect to see what's inside, raw — not an aggregate.
## Context
Observations above are based on Superset `1.1.0`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
