[MXS-4059] Make query editor visualization feature easier to use Created: 2022-03-24  Updated: 2022-04-12  Resolved: 2022-04-12

Status: Closed
Project: MariaDB MaxScale
Component/s: maxgui
Affects Version/s: 6.2.1
Fix Version/s: 6.3.1

Type: Bug Priority: Major
Reporter: Naresh Chandra Assignee: Duong Thien Ly
Resolution: Fixed Votes: 0
Labels: None

Attachments: PNG File image-2022-03-24-12-23-01-517.png     PNG File image-2022-03-24-12-23-36-528.png     PNG File image-2022-03-24-12-24-18-010.png    
Issue Links:
Relates
relates to MXS-4030 Query Editor: Y axis dropdown doesn't... Closed
Sprint: MXS-SPRINT-154, MXS-SPRINT-155

 Description   

In the query editor, if we try to visualize the data, when we select the y-axis list, but we don't see all the columns list in the y-axis but we can able to see all the columns in the x-axis list.

Actual Result set columns Are:

X-Axis:

Y-Axis:

If the X-Axis value is a number and the Y-Axis value is a string, the graph should recognize and auto-revert the graph accordingly if it's possible.
If the X-Axis value is a string and the Y-Axis value is a number or if both X-Axis and Y-Axis values are numbers, draw the graph normally.
If both axes' values are strings, the graph would still be drawn but the value for the X-axis will be the index value.



 Comments   
Comment by Duong Thien Ly [ 2022-03-24 ]

Hi naresh.chandra@copart.com, this is expected behavior. I assume the data type for the "Host" column is not a numeric type. The column for the Y-axis of the graph can only accept numeric types.

Comment by Naresh Chandra [ 2022-03-24 ]

okay Duong got it, But users don't know what is x-axis and y-axis, so can we add info button and give some info popup show that they can select the columns accordingly.

Comment by Duong Thien Ly [ 2022-03-24 ]

Yes, that's a good point. Do you mind if I edit the title and the description to match that requirement?

Comment by Naresh Chandra [ 2022-03-24 ]

Yeah, that's fine. you can edit accordingly.

Generated at Thu Feb 08 04:25:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.