-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Sub-aggregations should be sorted globally #14536
Comments
yes, is there any plan to fix this issue asap? |
Vote for this issue as well. |
+1 |
+1....Please! |
+1 |
1 similar comment
+1 |
+1 |
+1 |
1 similar comment
+1 |
+1 I think the heatmap chart can be used a lot when we hope to find relationship between two variables. If there's one variable that's randomly listed, the relationship can hardly be find, which makes heatmap meaningless. Maybe, vega is for this requirement? |
+1 on this. Attempting to create a heatmap for common monitor sizes, it's very difficult to view this data property without being able order both axes correctly. |
+1 |
+1 |
+1 |
+1 In all my use cases I could just simply set the order manually, that would be a great improvement. I get what happens behind the scenes but it's tedious every time someone else encounters the problem and I have to explain why the plot is screwed up. Just like lubobill1990 says, it's hard to see some patterns when the second agg is all over the place. |
+1 Trying to create a pretty rudimentary HourOfDay by DayOfWeek heatmap and can't I also agree with @rwhit . It is a bug, as the UI suggests to the User that it is possible to sort by both X & Y axes, when in fact it's not. |
This has now been an Open issue for 25 months, any update @timroes ? |
+1 |
If you use the |
+1 |
1 similar comment
+1 |
This is not just on heatmaps, the same problem happens with line graphs as well. |
Duplicate of #86184 |
+1 |
+20 |
Describe the feature:
Currently, a visualization with sub-buckets such as a heat map, if both the X and Y axes have a natural order, there is no way to get both axes to sort in the expected way. The sub-aggregations are sorted within the scope of each main bucket. I believe they should instead be sorted globally according to the chosen sort criteria (or, if there is a use case where the current behavior is preferable, this should be a user option).
Example:
(from https://discuss.elastic.co/t/ordering-for-both-axes-of-heatmap/104589 )
Here is a heatmap. The "class" and "investigation number" are both numeric values which ought to be presented in order:
As you can see the Y "class" axis is not in the ascending order by term as I wanted.
I can give the Y axis priority so that it does appear in the correct order like this:
But now the investigation number is not in increasing order. There is currently no way to get both axes in the expected order.
The text was updated successfully, but these errors were encountered: