Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.

Last update: Dec 30, 2022

Overview

Redash is designed to enable anyone, regardless of the level of technical sophistication, to harness the power of data big and small. SQL users leverage Redash to explore, query, visualize, and share data from any data sources. Their work in turn enables anybody in their organization to use the data. Every day, millions of users at thousands of organizations around the world use Redash to develop insights and make data-driven decisions.

Redash features:

Browser-based: Everything in your browser, with a shareable URL.
Ease-of-use: Become immediately productive with data without the need to master complex software.
Query editor: Quickly compose SQL and NoSQL queries with a schema browser and auto-complete.
Visualization and dashboards: Create beautiful visualizations with drag and drop, and combine them into a single dashboard.
Sharing: Collaborate easily by sharing visualizations and their associated queries, enabling peer review of reports and queries.
Schedule refreshes: Automatically update your charts and dashboards at regular intervals you define.
Alerts: Define conditions and be alerted instantly when your data changes.
REST API: Everything that can be done in the UI is also available through REST API.
Broad support for data sources: Extensible data source API with native support for a long list of common databases and platforms.

Getting Started

Setting up Redash instance (includes links to ready-made AWS/GCE images).
Documentation.

Supported Data Sources

Redash supports more than 35 SQL and NoSQL data sources. It can also be extended to support more. Below is a list of built-in sources:

Amazon Athena
Amazon DynamoDB
Amazon Redshift
Axibase Time Series Database
Cassandra
ClickHouse
CockroachDB
CSV
Databricks (Apache Spark)
DB2 by IBM
Druid
Elasticsearch
Firebolt
Google Analytics
Google BigQuery
Google Spreadsheets
Graphite
Greenplum
Hive
Impala
InfluxDB
JIRA
JSON
Apache Kylin
OmniSciDB (Formerly MapD)
MemSQL
Microsoft Azure Data Warehouse / Synapse
Microsoft Azure SQL Database
Microsoft SQL Server
MongoDB
MySQL
Oracle
PostgreSQL
Presto
Prometheus
Python
Qubole
Rockset
Salesforce
ScyllaDB
Shell Scripts
Snowflake
SQLite
TiDB
TreasureData
Vertica
Yandex AppMetrrica
Yandex Metrica

Getting Help

Issues: https://github.com/getredash/redash/issues
Discussion Forum: https://discuss.redash.io/

Reporting Bugs and Contributing Code

Want to report a bug or request a feature? Please open an issue.
Want to help us build Redash? Fork the project, edit in a dev environment and make a pull request. We need all the help we can get!

Security

Please email [email protected] to report any security vulnerabilities. We will acknowledge receipt of your vulnerability and strive to send you regular updates about our progress. If you're curious about the status of your disclosure please feel free to email us again. If you want to encrypt your disclosure email, you can use this PGP key.

License

BSD-2-Clause.

Comments

Parameter “Apply Changes” button
[x] Feature

Description

Following ux discussion in what-to-do-when-you-want-to-update-several-parameters-before-running-a-query

Applied for:

Dashboard level parameters

Widget level params

Query page

Visualization Embed

(And not for param mapping edit modal, as this is now a feature of <parameters>)

Mobile & Desktop Screenshots

Desktop

Mobile

Bigger button, not "floating"
opened by ranbena 36
Dashboard Parameters
Split Add Widget button (and modal) into two buttons (and modals): Add Widget and Add Textbox.

Implement new logic of mapping query parameters to dashboard parameters (as described in issue).

Screenshots:

Closes #1750, closes #2641.
Frontend UX enhancement Feature: Parameters Frontend: React
opened by kravets-levko 35
Add Dynamic Values to Date and Date Range Parameters
What type of PR is this? (check all applicable)

[x] Feature

Description

Allow Dynamic Values to Date and Date Range Parameters :tada:.

See preview below for details :)

Related Tickets & Documents

Closes #3009

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Frontend
opened by gabrieldutra 34
Migrate Data Sources and Alert Destinations pages to React
Description

Migrate Data Sources and Alert Destinations pages to React

Changes

General

[x] Migrate TypePicker to React

[x] Review TypePicker style

List Pages

[x] Data Sources

[x] Destinations

[x] Improve behavior for empty set

Create Pages

[x] Data Sources

[x] Select Type

[x] Configure Type

[x] Done

[x] Destinations

[x] Select Type

[x] Configure Type

[x] Done

Edit Pages

[x] Data Sources

[x] Destinations

To Do

[x] Routes /data_sources/new & /destinations/new auto-opening the modal

[x] Help using HelpTrigger

[x] Refine Edit forms

[x] Update Cypress tests

Possible Extra

Add edit & delete actions to the cards on List Pages (ref)

Notes

Data Sources and Destinations are very similar pages, however I'm not sure how much logic I should share. They are sharing TypePicker (renamed to CardsList) and DynamicForm, but to me it doesn't feel that they should share much more. I'll keep the idea of refactoring parts of it to avoid code duplication anyway.

Preview

Overview

Frontend Frontend: React
opened by gabrieldutra 33
Migrate Dashboards/Queries/Users list pages to React
[x] Create new base component based on /lib/list-ctrl.js (which is a common parent for mentioned pages);

[x] Migrate Dashboards list page;

[x] Migrate Queries list page;

[x] Migrate Users list page;

[x] Error handling

[x] <users-list-extra>

[x] Cleanup.

Screenshots:

Frontend Frontend: React
opened by kravets-levko 33
Refresh query when parameters update
What type of PR is this? (check all applicable)

[x] Feature

Description

This is a work on #2316.

So far, I've added a touch state to Query Parameters and it now refreshes query results whenever a parameter is modified (debounce already added). Next step will be to add an "Apply" button for input fields while refining UX.

[x] Refresh query when parameters are modified

[x] Add "Apply" button for input fields and let auto-refresh for the rest (Dropdowns, Time pickers)

[x] Remove button from #3752

Related Tickets & Documents

#2316

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Not yet :sleeping:
opened by gabrieldutra 30
Feature/query based parameter

Feature: Query based parameter (drop-down)

The feature is useful for our use-cases where parameters tend to be dynamic and comes from other queries. We have couple of use-cases where we will need such support. This is a feature available in a comparable product offering from Mode analytics (https://help.modeanalytics.com/articles/using-dynamic-parameters/).

The implementation is basically to use a saved query within redash as a parameter. Restriction for this query is that only first column will be used for options of the parameter and it must of a string format. By using saved queries for parameter, we get all the goodies of redash queries (caching, refreshing etc.)

opened by rohithmenon 30
Revisit Plotly integration
Issue getredash/redash#2117

Improved code quality of chart component.

Implemented auto-size for axis (and removed unnecessary X-Axis Height option from editor).

Add new stacking options (fixes getredash/redash#1902).

Fix y-axis min/max options (getredash/redash#1832).

Fix chart labels + better formatting (getredash/redash#1326).

Fix bug with staking negative values (bar, line and area charts). Fix percent value stacking (bar, line and area charts). Implement stacking for line charts (getredash/redash#2116).

Option to always show labels on chart (bar, line and area charts - getredash/redash/issues/1254).
opened by kravets-levko 28
Docker deployment support
Add docker support (see #450).

Couple things to note:

I removed imagemin task in grunt since

It is obsolete and cannot be downloaded anymore (at least on my side). It can block building so I removed it.

It is useless, I mean, in re:dash

Example docker-compose.yaml is added.

Made service listen on 0.0.0.0 instead of only 127.0.0.1. So docker containers can accept incoming traffic then.
opened by tjwudi 28
Dashboard grid React migration #1
[x] Refactor

Description

Since gridstack has no React implementation, migrated to react-grid-layout.

Closes #3285.

Included

[x] Draggable/Resizable widgets

[x] Added / Removed widgets

[x] Dashboard config compliance

[x] Public dashboard

[x] Layout auto-save

[x] Edit/Preview modes

[x] Tests passing (wip #3726)

[x] Auto Save/Fail/Retry

[x] Grid markings

Not included (tests skipped)

Single column breakpoint (upcoming PR)

Widget auto-height (wip)

Changed

Only one resize handle (bottom-right).

Fixes #3202 (test allows opening menu after removal now unskipped)

Fixes #3721.

Known Issues

~~Removing widget in preview mode, generates js error.~~

~~Dragging/Resizing but no change - still a saving indication is triggered~~

Widgets draggable beyond page as reported here. Leaving unattended.

Feature: Dashboards Frontend: React
opened by ranbena 26

Move to Python 3: dependencies status

Thanks to the work of @cclauss our code is (more) ready for Python 3. I also ran caniusepython3 on our requirements files and the results are very encouraging:

$ caniusepython3 --requirements requirements.txt
Finding and checking dependencies ...

You need 5 projects to transition to Python 3.
Of those 5 projects, 4 have no direct dependencies blocking their transition:

  chromelogger
  flask-sslify
  python-geoip (which is blocking python-geoip-geolite2)
  restrictedpython

python-geoip has a Python 3 compatible alternative (python-geoip-python3)
Latest master version of flask-sslify is marked as Python 3 compatible, but no new version was released for a long time.
chromelogger is unknown but we can either drop it or update to support Python 3 (~140 lines of code).
restrictedpython has an unreleased version 4 that supports Python 3.

$ caniusepython3 --requirements requirements_all_ds.txt
Finding and checking dependencies ...

You need 1 project to transition to Python 3.
Of that 1 project, 1 has no direct dependencies blocking its transition:

  pyhive

I'm not sure why pyhive is marked as not supported, because it is. Maybe we just need to update the version.

$ caniusepython3 --requirements requirements_dev.txt
Finding and checking dependencies ...

You need 1 project to transition to Python 3.
Of that 1 project, 1 has no direct dependencies blocking its transition:

  pytest-watch

I'm not sure about the state of pytest-watch, but we can always remove it.

Backend Tech Debt Python 3

opened by arikfr 26

Request feature - Add support to multiple Currency on Formatting Numbers in Visualizations

Add support to multiple currency on Formatting Numbers in Visualizations.

Documentation: https://redash.io/help/user-guide/visualizations/formatting-numbers Today just allow $(Dollar), need add possibility to allow multiple currency signals like R$(Brasil Real), ¥(Yen / Yuan), €(Euro) and others.

Reference of issue: https://github.com/getredash/website/issues/661
Support Question

opened by ViniciusFXavier 0
Make the database reencrypt script safer
What type of PR is this?

[x] Bug Fix

Description

The current reencrypt script (manage database reencrypt old_key new_key, as described in the docs) works nicely when databases are consistent.

However, there are some scenarios where a database encryption may become inconsistent, and this script can be really helpful with just some minor adjustments.

For exemple, in our case, we were upgrading from V8 directly to V10. As we saw there was a new REDASH_SECRET_KEY, we set this new key with a new value. However, during the db migration, only one table was migrated (we're still not sure how that happened).

The result was that the encryption key used in the data_sources table became different from the notification_destinations table in production. Hence, we could not access our Alert Destinations page in the browser.

It is also not hard to think of other inconsistency cases, such as different rows inside those tables having different encryption keys.

In our case, if we ran this script as it was, it would break immediately because the data_sources table runs first, making it impossible to fix the notification_destinations rows. Also, we were not sure if running this with a possibly invalid token could somehow break our data sources.

With the small proposed change, we make the reencrypt script safer to run. This way, it will run row by row, and only change the encryption if old_key is able to decrypt the data in the first place. If it isn't, then the script simply skips that row.

What do you think? If approved, I can also update the docs here.

How is this tested?

[ ] Unit tests (pytest, jest)

[ ] E2E Tests (Cypress)

[x] Manually

[ ] N/A

It is just a small update to a script that had no automatic testing in the first place.

The way I tested was simply building redash locally and playing with different encryption keys in the env vars.

Related Tickets & Documents

I'll update the docs if you agree with the changes :)

The idea is to just to make it clearer in the docs that the reencrypt script is safe to use, even if you are not sure about the decryption key.
opened by flaviomax 0
Update snowflake-connector-python
The Snowflake parameter MULTI_STATEMENT_COUNT can be altered in this version, which will solve the "Multiple SQL statements in a single API call are not supported; use one API call per statement instead." error

What type of PR is this?

[x] Refactor

Description

Update requirements for snowflake-connector-python

How is this tested?

[x] N/A
opened by yonatang-cyera 0
Sankey graph not displaying
Issue Summary

Sankey graph (and also Sunburst) does not display. I'm creating the graph using the simple case described in PR #5286 and the result is shown below:

Chrome Version 108.0.5359.125 (Official Build) (64-bit) Windows Redash Version: 10.1.0 (2589bef1)

Steps to Reproduce

Create and execute the following query:

select '0', '1', '2', 10 as value union select '0', '0', '3', 5 as value union select '1', '3', '0', 20 as value

Create a Sankey or Sunburst graph.

Observe blank graph area.

The following alternative simple case also does not work:

with base(stage1,stage2,stage3,value) AS ( SELECT * FROM (VALUES ('a', 'b', 'c', 1), ('a', 'b', 'd', 1), ('z', 'b', 'd', 2), ('z', 'x', 'c',1), ('a', null, 'c', 17))) SELECT * FROM base

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?

Technical details:

Redash Version: 10.1.0 (2589bef1)

Browser/OS: Chrome Version 108.0.5359.125 (Official Build) (64-bit) Windows

How did you install Redash: Setup script on single host. Migrated to 10.1.0 following migration instructions.
opened by ZeroParticle 0
Web UI doesn't allow removing bad SSL certs from Data Sources
Issue Summary

#4871 added support for uploading SSL certs. However, there is no option to remove bad/incorrect SSL certs.

If a bad cert is uploaded (e.g. while trying to set up an SSL Mode of Verify Full), then even if the user reverts to an SSL Mode of Require, the user will see errors like "SSL error: certificate verify failed" when clicking Test Connection, etc.

Steps to Reproduce

Upload any acceptable file as SSL Root Certificate (just don't choose the correct certificate)

Click Save

To undo this configuration, the user can use the CLI, like:

./manage.py ds list # Copy the data source's name. # Copy the data source's options and delete the `sslrootcertFile` key. ./manage.py ds edit NAME --options OPTIONS

Technical details:

Redash Version: redash/redash:10.1.0.b50633 image

Browser/OS: macOS, Safari (not relevant)

How did you install Redash: Docker Compose
opened by jpmckinney 0
Bump qs from 6.5.2 to 6.5.3 in /viz-lib
Bumps qs from 6.5.2 to 6.5.3.

Changelog

Sourced from qs's changelog.

6.5.3

[Fix] parse: ignore __proto__ keys (#428)

[Fix] utils.merge: avoid a crash with a null target and a truthy non-array source

[Fix] correctly parse nested arrays

[Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (#279)

[Fix] utils: merge: fix crash when source is a truthy primitive & no options are provided

[Fix] when parseArrays is false, properly handle keys ending in []

[Fix] fix for an impossible situation: when the formatter is called with a non-string value

[Fix] utils.merge: avoid a crash with a null target and an array source

[Refactor] utils: reduce observable [[Get]]s

[Refactor] use cached Array.isArray

[Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (#269)

[Refactor] parse: only need to reassign the var once

[Robustness] stringify: avoid relying on a global undefined (#427)

[readme] remove travis badge; add github actions/codecov badges; update URLs

[Docs] Clean up license text so it’s properly detected as BSD-3-Clause

[Docs] Clarify the need for "arrayLimit" option

[meta] fix README.md (#399)

[meta] add FUNDING.yml

[actions] backport actions from main

[Tests] always use String(x) over x.toString()

[Tests] remove nonexistent tape option

[Dev Deps] backport from main

Commits

298bfa5 v6.5.3

ed0f5dc [Fix] parse: ignore __proto__ keys (#428)

691e739 [Robustness] stringify: avoid relying on a global undefined (#427)

1072d57 [readme] remove travis badge; add github actions/codecov badges; update URLs

12ac1c4 [meta] fix README.md (#399)

0338716 [actions] backport actions from main

5639c20 Clean up license text so it’s properly detected as BSD-3-Clause

51b8a0b add FUNDING.yml

45f6759 [Fix] fix for an impossible situation: when the formatter is called with a no...

f814a7f [Dev Deps] backport from main

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies javascript
opened by dependabot[bot] 0

Releases(v10.1.0)

v10.1.0(Nov 24, 2021)
Docker Tag: redash/redash:10.1.0.b50633

Summary

This release includes fixes for three security vulnerabilities (click the links for complete details to see whether your installation is affected):

Insecure default configuration affects installations where REDASH_COOKIE_SECRET is not set explicitly (CVE-2021-41192)

SSRF vulnerability affects installations that enabled URL-loading data sources (CVE-2021-43780)

Incorrect usage of state parameter in OAuth client code affects installations where Google Login is enabled (CVE-2021-43777)

It also incorporates several fixes from master that merged after the V10.0 release.

See CHANGELOG for the full release notes.

Huge thanks to Ian Carroll and another reporter who preferred to remain anonymous for responsibly disclosing these vulnerabilities.

Upgrading

From V10.0:

Follow our standard upgrade process (reproduced below).

Make sure to backup your data. You only need to backup Redash’s PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) as the data in Redis is transient.

Change directory to /opt/redash.

Update /opt/redash/docker-compose.yml Redash image reference to redash/redash:10.1.0.b50633

Stop Redash services: docker-compose stop server scheduler scheduled_worker adhoc_worker (you might need to list additional services if you updated your configuration)

(No migrations are needed when upgrading from 10.0)

Read the Impact segment at this link. If your installation is affected, follow the instructions under the Patches heading to secure the secret fields in your database.

Start services with docker-compose up -d

From V9:

Follow the same steps as V10 but for step 5:

Apply migration: docker-compose run --rm server manage db upgrade

From V8 or earlier

Follow the complete steps outlined in the V10.0 release but use this Docker Tag in step 3: redash/redash:10.1.0.b50633

Read the Impact segment at this link. If your installation is affected, follow the instructions under the Patches heading to secure the secret fields in your database.

Source code(tar.gz)
Source code(zip)
v10.0.0(Oct 2, 2021)
Docker Tag: redash/redash:10.0.0.b50363

See CHANGELOG for the full release notes.

How to Upgrade

Complete upgrade instructions for those coming from V8 -> V10 appear below.

Note: V10 is the first non-beta Redash release since V8. So we expect most users upgrading to V10 are coming from V8. The upgrade from V8->V10 is like any other, but since RQ replaced Celery in this version there are a couple extra modifications that need to be done in your docker-compose.yml.

If you already run the V9-beta release you already made these changes. You can use the standard upgrade instructions instead.

These steps are performed on the server that runs Docker.

Make sure to backup your data. You only need to backup Redash’s PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) as the data in Redis is transient. Note: If you just deployed a Redash V8 AMI and have not used it, you can skip this step.

cd /opt/redash

Update opt/redash/docker-compose.yml to reference the docker image you want to upgrade to: redash/redash:10.0.0.b50363

Under services.scheduler.environment omit QUEUES and WORKERS_COUNT and omit environment altogether if it is empty.

5. Under services, add a new service for general RQ jobs:

worker: <<: *redash-service command: worker environment: QUEUES: "periodic emails default" WORKERS_COUNT: 1

Stop Redash services: docker-compose stop server scheduler scheduled_worker adhoc_worker (you might need to list additional services if you defined them in your docker-compose.yml previously)

Force a recreation of your containers with docker-compose up --force-recreate --build

Run the necessary migrations with docker-compose run --rm server manage db upgrade

Restart the containers docker-compose up -d

Dashboard URL Changes

Dashboard URLs now include the dashboard id and slug.

For example, given a dashboard with the slug account-overview and an id of 251:

Before https://redash.app/dashboards/account-overview

After https://redash.app/dashboards/251-account-overview

The dashboard can also be reached using the new /dashboard (notice this is singular) endpoint. It accepts either an ID or a slug:

https://redash.app/dashboard/251

https://redash.app/dashboard/account-overview

Either of these will redirect to the After link above. Dashboard ID's are guaranteed to be unique. But dashboards can share the same slug. If a user visits /dashboard/<some slug> and more than one dashboard exists with that slug, they will be redirected to the earliest created dashboard with that slug.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v10.0.0-beta(Jun 21, 2021)
Docker Tag: redash/redash:10.0.0-beta.b49597

See CHANGELOG for the full release notes.

Special instructions for upgrading from V8 or earlier

Typically, if you are running your own instance of Redash and wish to upgrade, you would simply modify the Docker tag in your docker-compose.yml file. Since RQ has replaced Celery in this version, there are a couple extra modifications that need to be done in your docker-compose.yml:

Under services/scheduler/environment, omit QUEUES and WORKERS_COUNT (and omit environment altogether if it is empty).

Under services, add a new service for general RQ jobs:

worker: <<: *redash-service command: worker environment: QUEUES: "periodic emails default" WORKERS_COUNT: 1

Following that, force a recreation of your containers with docker-compose up --force-recreate --build and you should be good to go.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v9.0.0-beta(Jun 14, 2020)
Docker Tag: redash/redash:9.0.0-beta.b42121.

See CHANGELOG for the full release notes.

Upgrading

Typically, if you are running your own instance of Redash and wish to upgrade, you would simply modify the Docker tag in your docker-compose.yml file. Since RQ has replaced Celery in this version, there are a couple extra modifications that need to be done in your docker-compose.yml:

Under services/scheduler/environment, omit QUEUES and WORKERS_COUNT (and omit environment altogether if it is empty).

Under services, add a new service for general RQ jobs:

worker: <<: *redash-service command: worker environment: QUEUES: "periodic emails default" WORKERS_COUNT: 1

Following that, force a recreation of your containers with docker-compose up --force-recreate --build and you should be good to go.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v8.0.0(Oct 28, 2019)
Docker Tag: redash/redash:8.0.0.b32245.

See CHANGELOG for the full release notes.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v8.0.0-beta.2(Sep 18, 2019)
Docker Tag: redash/redash:8.0.0-beta.2.b29352.

See CHANGELOG for the full release notes.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v7.0.0(Mar 25, 2019)
Please read the following before upgrading:

If you're using the tarball deployment and not Docker, you might need to manually update some of the dependencies. Compare your current Python dependencies with the ones in the requirements*.txt files.

This release adds encryption of your data sources configuration. By default it will use the REDASH_COOKIE_SECRET as encryption key. But we recommend setting a new key for it using the REDASH_SECRET_KEY environment variable. Note that you need to set this before running migrations. Otherwise everything will be encrypted with REDSAH_COOKIE_SECRET.

See CHANGELOG for the full release notes.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v6.0.0(Dec 17, 2018)
Before upgrading to v6.0.0 make sure to clear out the Celery queue (unless upgrade from v6.0.0-beta).

This is the final release of v6.0.0. See v6.0.0-beta for details of what's new in v6.0.0. This release includes only fixes from regressions introduces in the beta version.

This release had contributions from 5 people: @rauchy, @denisov-vlad, @arikfr, @ariarijp, and @gabrieldutra. Thank you, everyone 🙏

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v6.0.0-beta(Dec 4, 2018)
Redash v6 beta is now available! 🙌 This release was 2 months in the making and it is full with good stuff!

We have 5 new data sources: Databricks, IBM DB2, Kylin, Druid and Rockset. ⌗

There are fixes and improvements to 11 existing data sources (MySQL, Redshift, Postgres, MongoDB, Google BigQuery, Vertica, TreasureData, Presto, ClickHouse, Google Sheets and Google Analytics).

The Query Results data source can now load cached results, just use the cached_query_ prefix instead of query_.

On the visualizations front we added a Heatmap visualization and did updated the table and counter visualizations.

Alerts got some fixes and a new destination: PagerDuty.

If the live autocomplete in the code editor annoys you, you can disable it now (although we're working to make it better, see #3092).

Fast queries will now load faster. :running_man:

We improved the layout of visualizations and content on smaller screen sizes. 📱

For those of you who like sharing, you can now enable the ability to share ownership of queries and dashboards and let others to edit them. Check the Settings page to enable this feature.

There were also important changes to the code and infrastructure:

More components moved to React.

We switched to Webpack 4 with the help of @dmonego.

We upgraded to Celery 4 with the help of @emtwo, @jezdez, @mashrikt and @atharvai.

We started moving towards Python 3 for our backend. The first step was to make sure our code pass basic sanity tests with Flake 8, which was implemented by @cclauss.

We improved our testing on the frontend by adding setup for Jest tests and E2E testing using Cypress (@gabrieldutra).

Each pull request now gets a deploy preview using Netlify to easily test frontend changes.

This is just a summary, you're welcome to review the full CHANGELOG.

This release had contributions from 38 people: @arikfr, @kravets-levko, @jezdez, @kyoshidajp, @kocsmy, @alison985, @gabrieldutra, @washort, @GitSumito, @emtwo, @rauchy, @alexanderlz, @denisov-vlad, @ariarijp, @yoavbls, @zhujunsan, @sjakthol, @koooge, @SakuradaJun, @dmonego, @Udomomo, @cclauss, @combineads, @zaimy, @Trigl, @ralphilius, @jodevsa, @deecay, @igorcanadi, @pashaxp, @hoangphuoc25, @toph, @burnash, @wankdanker, @Yossi-a, @Rovel, @kadrach, and @nicof38. Thank you, everyone 🙏

Before doing an upgrade, please make sure you have a backup.

Because of the Celery upgrade, before upgrading to this version please make sure to clear out your Celery queues.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn’t help, you can ask for help on the forum.

Happy querying :nerd_face:
Source code(tar.gz)
Source code(zip)
v5.0.2(Oct 18, 2018)
v5.0.2:

Fix: prevent Open Redirect vulnerability.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v5.0.1(Sep 28, 2018)
V5.0.1:

Upgraded Celery version to 3.1.26 to make upgrade to Celery 4 easier.

Added support for JWT authentication (for services like Cloudflare Access or Google IAP).

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v5.0.0(Sep 21, 2018)
Final release for V5. Most of the changes were already in the beta release of V5, but this includes several fixes along with UI improvements.

🙏 Thanks to @arikfr, @jezdez, @kravets-levko, @alison985, @kocsmy, @yossi-a, @tdsmith, @nasmithan, @jrbenny35, @sjakthol, @ariarijp and @combineads who contributed to this release.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v4.0.2(Sep 20, 2018)
This is a security release for V4 users. You can find full details on what it fixes and its importance in the release blog post.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v5.0.0-beta(Aug 6, 2018)
This is the first beta of the V5 release (and hopefully the last one). This version includes a lot of exciting new additions along with bug fixes and other changes.

Some notable changes:

Extensive work on parameters UI:

New Date Range parameter type.

UI for creating new parameters.

Support for Now/Today as default value of date/time parameter.

Tagging and favorites ⭐️ support for queries and dashboards.

Users list page was improved (search, additional information) and you can now disable users.

Query editor improvements: additional keyboard shortcuts and support for searching in query text.

Visualizations improvements: option to select colors of pie chart sectors, X Axis type auto detect and option to format values, labels and tooltips.

Data Sources:

Support for Yandex Metrika and AppMetrika.

BigQuery: location property support and schema will load all tables now.

Elasticsearch: stop sending source_content_type parameter which wasn't supported in older versions.

Started migrating the frontend codebase to React.

And much more!

🙏 Thanks to @kravets-levko, @arikfr, @ariarijp, @alison985, @kyoshidajp, @kocsmy, @denisov-vlad, @deecay, @yuua, @emtwo, @Pablohn26, @sieben, @atharvai, @matsumo, @tdawber, @innovia, @gabrieldutra, @coreyhuinker, @maxv, @sjakthol, @mtrbean and @washort who contributed to this release!

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Docker image and updated tarball will be ready soon.

Happy querying 🤓
Source code(tar.gz)
Source code(zip)
v4.0.1(May 2, 2018)
v4.0.1 is a recommended upgrade that includes several bug fixes, small changes and improved dashboard refresh UX.

As always huge thanks to everyone who contributed to this release. 🙏

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Happy querying 🤓
Source code(tar.gz)
Source code(zip)
v4.0.0(Apr 16, 2018)
V4 is finally out. 🎁 We used the feedback from RC1 and our hosted customers to fix some performance issues in the RC1 release. @kravets-levko worked hard so you will get smooth performance with the new dashboards layout editor.

This release includes 35 changes, features and bug fixes from @alon710, @arikfr, @deecay, @fmy, @idalin, @kravets-levko, @tnetennba3, @toru and @valentin2105. 🙏 🙏 🙏 This includes new Choropleth map visualization, Mattermost support and more.

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Docker image and updated tarball will be ready soon.

Happy querying 🤓
Source code(tar.gz)
Source code(zip)
v4.0.0-rc.1(Mar 5, 2018)
This is a follow up release to the v4.0.0-beta and hopefully the last release before the full release of v4.0.0. It includes fixes to some bugs introduced in the beta version (like public dashboards or embeds not rendering), but also new features like the funnel visualization and more (CHANGELOG).

This is a beta release, to upgrade to this release from an existing deployment run sudo bin/upgrade --channel beta. If you use a Docker based deployment you do not need to use this script, but rather update your image reference.

As always this wouldn't be possible without the help of all the people who contributed code in this release: @kravets-levko, @arikfr, @kocsmy, @jezdez, @benmanns, @ariarijp, @tonyjiangh and @jubel-han. 🙏🙏🙏

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v4.0.0-beta(Feb 15, 2018)
This is a very exciting release 🤩 that was a long time in the making 👷. It includes a fully updated user interface that should provide a much nicer experience, along with many new features and improvements:

Table visualization customization along with new column types (image, JSON & URL).

Dashboard layout editing (full control over widget height/width).

Updated chart visualization (mostly bug fixes) and settings for the cohort visualization.

BigQuery and Athena queries now show the amount of data scanned, so you know how much the query costs you. On top of that we have new data sources (MapD & CockroachDB) and improvements to other data sources (MongoDB, Salesforce, Redshift, Oracle and Elasticsearch).

This is only the tip of the iceberg, see the full list of changes in the CHANGELOG.

This is a beta release, to upgrade to this release from an existing deployment run sudo bin/upgrade --channel beta. If you use a Docker based deployment the Docker tag is 4.0.0-beta.b3690.

As always this wouldn't be possible without the help of all the people who contributed code in this release: @arikfr, @kravets-levko, @kyoshidajp, @ariarijp, @sjakthol, @kocsmy, @jezdez, @deecay, @kakakakakku, @bamboo-yujiro, @tonyjiangh, @washort, @jasonsmithj, @shinji19, @arjan, @gramakri, @doddjc21, @cdessanti, @yershalom, @miketheman, @crooy, @alexdrans, @javier-sanz, @negibouze, @mayconbordin and @rgjodekerken. 🙏🙏🙏

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v3.0.0(Dec 31, 2017)
Great things in this version like the long awaited Select All for filters, query based parameters, improvements to existing data sources (MongoDB, Redshift, MySQL) but and new data sources (Prometheus, Azure SQL Data Warehouse) and some more.

This release wouldn’t be possible without the contributions of @myouju, @jezdez, @hhamalai, @atharvai, @kitsuyui, @yershalom, @fan-t-endo, @TylerBrock, @deecay, @rohithmenon, @Posnet, @amarjayr, @kyoshidajp, @meinac, @muddydixon, @cclauss, @alexmuller, @akiray03, @aterreno, @44px, @alison985, @isomura, @sylvain, @cyriac, @yutannihilation, @kravets-levko and @queeno. :clap: :clap:

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v2.0.1(Oct 22, 2017)
This is a patch release, that adds support for Redshift ACM certificates (see #2044 for details).

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Source code(tar.gz)
Source code(zip)
v2.0.0(Aug 8, 2017)
Finally a new major release! 🙌 You can review the full CHANGELOG, but some highlights of this release:

Direct Athena data source type (no more need for the Java proxy 👊 ).

New MemSQL data source type and updates/fixes to the MySQL, Google Analytics, Presto, MongoDB, Cassandra, JIRA, TreasureData, InfluxDB, MSSQL, PostgreSQL, and BigQuery data sources.

New Plotly based Box Plot visualization along with improvements to the Pivot Table, cohort and counter visualizations.

List parameter type.

Friendly API key dialog for queries along with usage examples.

Auto-publish queries when they are named (with option to disable; see #1830).

This release wouldn't be possible without the help of @mfouilleul, @dotneet, @rmakulov, @deecay, @fbertsch, @rockwotj, @alexanderlz, @laughingman7743, @ziahamza, @yamamanx, @miketheman, @eyalzek, @alexpekurovsky, @ahamino, @jvanegmond, @suemoc, @44px, @amarjayr, @unixwitch, @danielerapati, @yershalom, @msnider, and @alison985 -- thank you, everyone 🙏 .

Before doing an upgrade, please make sure you have a backup.

If you have any issues, please refer to the troubleshooting section in the upgrade guide.

If the upgrade guide doesn't help, you can ask for help on the forum.

Full CHANGELOG for this release.
Source code(tar.gz)
Source code(zip)
v1.0.3(Apr 18, 2017)
New hotfix release that fixes a performance issue in v1.0.1 and a few other small fixes that got in.

Full CHANGELOG for this release. If you're upgrading from a pre-v1.0 version, checkout the CHANGELOG for previous releases as well (v1.0.1, RC2, RC1).

If you were using the MULTI_ORG or ALLOW_PARAMETERS_IN_EMBEDS options, then they are currently not supported but planned to be supported in the next release.

If you're upgrading to this version from pre v1.0.0 release, before upgrading, please make sure to do the following changes to your /opt/redash/.env file:

If you have local PostreSQL database, you will need to update the URL from postgresql://redash to postgresql:///redash.

Remove the REDASH_STATIC_ASSETS_PATH definition.

Make sure to complete these changes before doing the actual upgrade.

We have a new upgrade script that supports multiple release channels. To deploy this version run: sudo upgrade.

You can upgrade to v1.0.0 and later only from v0.12.0, so if you have an older version, run: sudo upgrade --channel legacy first and then sudo upgrade.
Source code(tar.gz)
Source code(zip)
v1.0.2(Apr 18, 2017)
New hotfix release that fixes a performance issue in v1.0.1 and a few other small fixes that got in.

Full CHANGELOG for this release. If you're upgrading from a pre-v1.0 version, checkout the CHANGELOG for previous releases as well (v1.0.1, RC2, RC1).

If you were using the MULTI_ORG or ALLOW_PARAMETERS_IN_EMBEDS options, then they are currently not supported but planned to be supported in the next release.

If you're upgrading to this version from pre v1.0.0 release, before upgrading, please make sure to do the following changes to your /opt/redash/.env file:

If you have local PostreSQL database, you will need to update the URL from postgresql://redash to postgresql:///redash.

Remove the REDASH_STATIC_ASSETS_PATH definition.

Make sure to complete these changes before doing the actual upgrade.

We have a new upgrade script that supports multiple release channels. To deploy this version run: sudo upgrade.

You can upgrade to v1.0.0 and later only from v0.12.0, so if you have an older version, run: sudo upgrade --channel legacy first and then sudo upgrade.
Source code(tar.gz)
Source code(zip)
v1.0.1(Apr 2, 2017)
This is the final release for v1 🎉 (tagged as v1.0.1 to trigger new version notification for the RC versions users).

Full CHANGELOG for this release. If you're upgrading from a pre-v1.0 version, checkout the CHANGELOG for previous releases as well (RC2, RC1).

If you were using the MULTI_ORG or ALLOW_PARAMETERS_IN_EMBEDS options, then they are currently not supported but planned to be supported in the next release.

If you're upgrading to this version from pre v1.0.0 release, before upgrading, please make sure to do the following changes to your /opt/redash/.env file:

If you have local PostreSQL database, you will need to update the URL from postgresql://redash to postgresql:///redash.

Remove the REDASH_STATIC_ASSETS_PATH definition.

Make sure to complete these changes before doing the actual upgrade.

We have a new upgrade script that supports multiple release channels. To deploy this version run: sudo upgrade.

You can upgrade to v1.0.0 and later only from v0.12.0, so if you have an older version, run: sudo upgrade --channel legacy first and then sudo upgrade.
Source code(tar.gz)
Source code(zip)
v1.0.0-rc.2(Feb 26, 2017)
Second RC for the v1.0.0 release. We're getting closer to the final release. The more people will run these versions, and report issues (or submit fixes) the sooner we will have a stable release.

Full CHANGELOG for this release.

If you're upgrading to this version from pre v1.0.0 release, before upgrading, please make sure to do the following changes to your /opt/redash/.env file:

If you have local PostreSQL database, you will need to update the URL from postgresql://redash to postgresql:///redash.

Remove the REDASH_STATIC_ASSETS_PATH definition.

Make sure to complete these changes before doing the actual upgrade.

We have a new upgrade script that supports multiple release channels. To deploy this version run: sudo upgrade --channel beta.

You can upgrade to v1.0.0 only from v0.12.0, so if you have an older version, run: sudo upgrade --channel legacy first and then sudo upgrade --channel beta.
Source code(tar.gz)
Source code(zip)
v1.0.0-rc.1(Jan 31, 2017)
Finally, a true v1.0.0-rc.1 release!

Before upgrading to this version, please make sure to do the following changes to your /opt/redash/.env file:

If you have local PostreSQL database, you will need to update the URL from postgresql://redash to postgresql:///redash.

Remove the REDASH_STATIC_ASSETS_PATH definition.

Make sure to complete these changes before doing the actual upgrade.

We have a new upgrade script that supports multiple release channels. To deploy this version run: sudo upgrade --channel beta.

You can upgrade to v1.0.0 only from v0.12.0, so if you have an older version, run: sudo upgrade --channel legacy first and then sudo upgrade --channel beta.

Full CHANGELOG for this release.
Source code(tar.gz)
Source code(zip)
v0.12.0.b2449(Jul 3, 2016)

This version has been too long in the making and now finally released. Includes new visualizations, data sources, updated packages and numerous fixes and additions.

See CHANGELOG for full release notes.

Huge thanks to over 30 contributors (!) that participated in this release.
Source code(tar.gz)
Source code(zip)
redash.0.12.0.b2449.tar.gz(2.16 MB)
v0.11.1.b2095(Aug 2, 2016)

This is a hotfix release, which fixes an issue with email alerts in v0.11.0. For those who are upgrading from versions earlier than v0.11, see full release notes in v0.11.
Source code(tar.gz)
Source code(zip)
redash.0.11.1.b2095.tar.gz(2.27 MB)
v0.11.0.b2016(May 1, 2016)
The main features of this release are:

Alert Destinations: ability to define multiple destinations for alert notifications (currently implemented: HipChat, Slack, Webhook and email).

The long-awaited UI for query parameters (see example in #1069).

Also, this release includes numerous smaller features, improvements, and bug fixes.

A big thank you goes to all who contributed code and documentation in this release: @AntoineAugusti, @James226, @adamlwgriffiths, @alexdebrie, @anthony-coble, @ariarijp, @dheerajrav, @edwardsharp, @machira, @nabilblk, @ninneko, @ordd, @tomerben, @toru-takahashi, @vishesh92, @vorakumar and @whummer.

Added

d5e5b24 #1136: Feature: add --org option to all relevant CLI commands. (@adamlwgriffiths) 87e25f2 #1129: Feature: support for JSON query formatting (Mongo, ElasticSearch) (@arikfr) 6bb2716 #1121: Show error when failing to communicate with server (@arikfr) f21276e #1119: Feature: add UI to delete alerts (@arikfr) 8656540 #1069: Feature: UI for query parameters (@arikfr) 790128c #1067: Feature: word cloud visualization (@anthony-coble) 8b73a2b #1098: Feature: UI for alert destinations & new destination types (@alexdebrie) 1fbeb5d #1092: Add Heroku support (@adamlwgriffiths) f64622d #1089: Add support for serialising UUID type within MSSQL #961 (@James226) 857caab #1085: Feature: API to pause a data source (@arikfr) 214aa3b #1060: Feature: support configuring user's groups with SAML (@vorakumar) e20a005 #1007: Issue#1006: Make bottom margin editable for Chart visualization (@vorakumar) 6e0dd2b #1063: Add support for date/time Y axis (@tomerben) b5a4a6b #979: Feature: Add CLI to edit group permissions (@ninneko) 6d495d2 #1014: Add server-side parameter handling for embeds (@whummer) 5255804 #1091: Add caching for queries used in embeds (@whummer)

Changed

0314313 #1149: Presto QueryRunner supports tinyint and smallint (@toru-takahashi) 8fa6fdb #1030: Make sure data sources list ordered by id (@arikfr) 8df822e #1141: Make create data source button more prominent (@arikfr) 96dd811 #1127: Mark basic_auth_password as secret (@adamlwgriffiths) ad65391 #1130: Improve Slack notification style (@AntoineAugusti) df637e3 #1116: Return meaningful error when there is no cached result. (@arikfr) 65635ec #1102: Switch to HipChat V2 API (@arikfr) 14fcf01 #1072: Remove counter from the tasks Done tab (as it always shows 50). #1047 (@arikfr) 1a1160e #1062: DynamoDB: Better exception handling (@arikfr) ed45dcb #1044: Improve vagrant flow (@staritza) 8b5dc8e #1036: Add optional block for more scripts in template (@arikfr)

Fixed

dbd48e1 #1143: Fix: use the email input type where needed (@ariarijp) 7445972 #1142: Fix: dates in filters might be duplicated (@arikfr) 5d0ed02 #1140: Fix: Hive should use the enabled variable (@arikfr) 392627d #1139: Fix: Impala data source referencing wrong variable (@arikfr) c5bfbba #1133: Fix: query scrolling issues (@vishesh92) c01d266 #1128: Fix: visualization options not updating after changing type (@arikfr) 6bc0e7a #1126: Fix #669: save fails when doing partial save of new query (@arikfr) 3ce27b9 #1118: Fix: remove alerts for archived queries (@arikfr) 4fabaae #1117: Fix #1052: filter not working for date/time values (@arikfr) c107c94 #1077: Fix: install needed dependencies to use Hive in Docker image (@nabilblk) abc790c #1115: Fix: allow non integers in alert reference value (@arikfr) 4ec473c #1110: Fix #1109: mixed group permissions resulting in wrong permission (@arikfr) 1ca5262 #1099: Fix RST syntax for links (@adamlwgriffiths) daa6c1c #1096: Fix typo in env variable VERSION_CHECK (@AntoineAugusti) cd06d27 #1095: Fix: use create_query permission for new query button. (@ordd) 2bc0b27 #1061: Fix: area chart stacking doesn't work (@machira) 8c21e91 #1108: Remove potnetially concurrency not safe code form enqueue_query (@arikfr) e831218 #1084: Fix #1049: duplicate alerts when data source belongs to multiple groups (@arikfr) 6edb0ca #1080: Fix typo (@jeffwidman) 64d7538 #1074: Fix: ElasticSearch wasn't using correct type names (@toyama0919) 3f90dd9 #1064: Fix: old task trackers were not really removed (@arikfr) e10ecd2 #1058: Bring back filters if dashboard filters are enabled (@AntoineAugusti) 701035f #1059: Fix: DynamoDB having issues when setting host (@arikfr) 2924d4f #1040: Small fixes to visualizations view (@arikfr) fec0d5f #1037: Fix: multi filter wasn't working with __ syntax (@dheerajrav) b066ce4 #1033: Fix: only ask for notification permissions if wasn't denied (@arikfr) 960c416 #1032: Fix: make sure we return dashboards only for current org only (@arikfr) b3844d3 #1029: Hive: close connection only if it exists (@arikfr)

Docs

6bb09d8 #1146: Docs: add a link to settings documentation. (@adamlwgriffiths) 095e759 #1103: Docs: add section about monitoring (@AntoineAugusti) e942486 #1090: Contributing Guide (@arikfr) 3037c4f #1066: Docs: command type-o fix. (@edwardsharp) 2ee0065 #1038: Add an ISSUE_TEMPLATE.md to direct people at the forum (@arikfr) f7322a4 #1021: Vagrant docs: add purging the cache step (@ariarijp)
Source code(tar.gz)
Source code(zip)
redash.0.11.0.b2016.tar.gz(2.27 MB)
v0.10.1.b1834(May 22, 2016)

This is a hotfix release, that includes #1064 (Fix: old task trackers were not removed). This is a recommended upgrade for all 0.10.0 users, as without it Redis's memory usage will keep growing without any limit.
Source code(tar.gz)
Source code(zip)
redash.0.10.1.b1834.tar.gz(2.28 MB)

Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.

Related tags

Overview

Getting Started

Supported Data Sources

Getting Help

Reporting Bugs and Contributing Code

Security

License

Comments

Description

Applied for:

Mobile & Desktop Screenshots

Desktop

Mobile

What type of PR is this? (check all applicable)

Description

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Description

Changes

To Do

Notes

Preview

Overview

Screenshots:

What type of PR is this? (check all applicable)

Description

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Feature: Query based parameter (drop-down)

Description

What type of PR is this?

Description

How is this tested?

Related Tickets & Documents

What type of PR is this?

Description

How is this tested?

Issue Summary

Steps to Reproduce

Technical details:

Issue Summary

Steps to Reproduce

Technical details:

6.5.3

Releases(v10.1.0)

v10.1.0(Nov 24, 2021)

Summary

Upgrading

From V10.0:

From V9:

From V8 or earlier

v10.0.0(Oct 2, 2021)

How to Upgrade

Dashboard URL Changes

v10.0.0-beta(Jun 21, 2021)

Special instructions for upgrading from V8 or earlier

v9.0.0-beta(Jun 14, 2020)

Upgrading

v8.0.0(Oct 28, 2019)

v8.0.0-beta.2(Sep 18, 2019)

v7.0.0(Mar 25, 2019)

v6.0.0(Dec 17, 2018)

v6.0.0-beta(Dec 4, 2018)

v5.0.2(Oct 18, 2018)

v5.0.1(Sep 28, 2018)

v5.0.0(Sep 21, 2018)

v4.0.2(Sep 20, 2018)

v5.0.0-beta(Aug 6, 2018)

v4.0.1(May 2, 2018)

v4.0.0(Apr 16, 2018)

v4.0.0-rc.1(Mar 5, 2018)

v4.0.0-beta(Feb 15, 2018)

v3.0.0(Dec 31, 2017)

v2.0.1(Oct 22, 2017)

v2.0.0(Aug 8, 2017)

v1.0.3(Apr 18, 2017)

v1.0.2(Apr 18, 2017)

v1.0.1(Apr 2, 2017)