Visualizations workflow & object about redash HOT 4 CLOSED

There was a case (EvMe's query 607), where the data was unsorted and had too many series, which resulted in HighCharts dying. When we revisit visualizations we should take into account limits for different visualizers, and prevent the user from killing his browser.

cc: @shayel.

from redash.

http://app.raw.densitydesign.org/#/

from redash.

@amirnissim this requires some changes on the backend too, but let's try to move forward without them and on Sunday we will discuss the needed changes.

Below is a "brain dump" about this feature, ask any questions you feel necessary:

Basically the idea is to have different types of visualizations, and the ability to create a new visualization from any dataset (query). Eventually, this will replace the "Chart" and "Cohort" static tabs.

Each visualization will define:

1. Name
2. Description
3. Properties (mandatory & optional + default values)
4. Rendering logic

When creating new visualization it will have:

1. query_id - reference to queries table
2. visualization_type - string
3. options - JSON
4. ?

Until we add the visualization object, let's start by creating the "infrastructure" for this in the frontend code.

In terms of UI, I think we will represent each visualization as a tab where we currently have the "Chart" and "Cohort" tabs and also have a "+" tab, where you define a new visualization.

from redash.

Test summary

63 • 0 • 0 • 0

Run details

Commit	a00c5a8
Started	Jun 23, 2019 8:44 AM UTC
Ended	Jun 23, 2019 8:52 AM UTC
Duration	07:24 💡
OS	linux Debian - 8.10
Browser	Electron 61.0.3163.100

View run in Cypress Dashboard ➡️

This comment has been generated by cypress-bot as a result of your project's GitHub integration settings. You can manage this integration in your project's settings in the Cypress Dashboard

from redash.