-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulse sparkline is rendering dot in the wrong place #2037
Comments
Is this in an email, I'm assuming? There's been a lot of Pulse-related fixes in the four releases that have come out since |
Hi @ryanatflip, you can update Metabase the same way you installed it. See the installation guide for more details |
if this is happening it would appear it's on SQL questions because i have several pulses that are rendering sparklines fine. |
But when I display the SQL query results as a graph, within the question,
the graph renders the complate sparkline. It's only when I set the question
up as a pulse when the sparkline is not complete.
|
I'm not sure I follow. from the screenshots shown above we'd expect to see 7 data points and they are all on the pulse sparkline. the problem as far as i understand it is that the dot on the sparkline is showing the first value instead of the last, as intended. |
The pulse rendering code is totally separate from the chart rendering code since we haven't been able to embed a good enough browser engine in the Java backend yet to render our JavaScript charts, so it's totally plausible there are bugs that affect one but not the other. If I were to guess, without trying your query or looking at the pulse rendering code, I'd say your query is returning the data in reverse chronological order, and we're not sorting it before picking the "last" data points for the labels and dot. If that's the case you should be able to work around this bug by switching your query's |
@salsakran @kdoh @mazameli , can one of you weigh in on the desired UX here? in this particular case the data points being highlighted are not the most recent points due to the fact that the data is sorted in the opposite order from what's expected. do we still want to highlight the most recent 2 data points? or is it okay that given the different sort order of the data that the oldest 2 data points are highlighted in this case? |
The intent of the pulse sparkline is to give the user the most recent value and show them the trend. The assumption "we expect the timeseries in ascending order" was (and is) reasonable. It would be nice if we would do the right thing even if this assumption is broken by the user. |
Yeah, if the user does something weird that would make the chart look reversed, it would be nice if we just flipped it back so that the most recent data point is on the right. |
…placed over the most recent value in the sparkline.
Please fill in the blanks, if relevant:
Here is the query:
SELECT
date(created_at), count(1) AS "Total"
From
listings
WHERE
date(created_at) > current_date - interval '7 days' AND
reward = false and
PRICE IS NOT NULL AND
status = 'available'
GROUP BY 1
ORDER BY 1 Desc;
the results are attatched
The text was updated successfully, but these errors were encountered: