The v3 release is almost ready! :smiley: There are great things coming 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.

:sunglasses: Those of you who want to give the beta version a try, can upgrade using: sudo bin/upgrade --channel beta (from /opt/redash/current). (Docker users can use the 3.0.0 tag)

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:

8 Likes

Good news! Will I be able to upgrade to v3 final from beta?

Awesome, is the datasets as datasource functionality opensourced by now? It was planned for 1+ (see link) and 3.0 seems to me to be very 1+ :slight_smile:

It seems so:

1 Like

Awesome. Thanks for sharing!

1 Like

Getting AttributeError: ‘module’ object has no attribute ‘SSL_ST_INIT’
error while migration… am i missing anything?

I got the same AttributeError: ‘module’ object has no attribute 'SSL_ST_INIT’…
then I did ‘sudo pip install pyOpenSSL==16.2.0’, it fixed the problem.

This v3 still considered beta? I see that the latest release on github is v2.0.1 (https://github.com/getredash/redash/releases) but at the same time I see that v3.0.0 doesn’t say “beta” on the changelog (https://github.com/getredash/redash/blob/master/CHANGELOG.md) and it’s listed as stable at version.redash (https://version.redash.io/)

1 Like

No, v3 is now the latest release.

1 Like

Is there a timeline for when there will be AMI’s or the provisioning script will be updated for v3.0.0? Currently the setup page still only references v2 (https://redash.io/help-onpremise/setup/setting-up-redash-instance.html)

I don’t plan on creating AMIs for v3, but I updated the provisioning script.

You can still use the AMIs and just run the upgrade script after.

1 Like

Awesome, thanks so much! Appreciate the quick response :slight_smile:

Doesn’t seem to work:

Starting Redash upgrade:
Found version: 2.0.0
Current version: 2.0.0+b2990
The found release is not newer than your current deployed release (2.0.0+b2990). Aborting upgrade.

Starting Redash upgrade:
Found version: 3.0.0
Current version: 2.0.1+b3080

Full CHANGELOG for this release: https://github.com/getredash/redash/blob/master/CHANGELOG.md
Continue with upgrade? (y/n): y
Downloading release tarball…
Unpacking to: redash.3.0.0.b3134…
Changing ownership to redash…
Linking .env file…
Installing new Python packages (if needed)…
Running migrations (if needed)…
Failed running: sudo -u redash bin/run ./manage.py db upgrade
Exit status: 1
Output:
Traceback (most recent call last):
File “/opt/redash/redash.3.0.0.b3134/manage.py”, line 6, in
from redash.cli import manager
File “/opt/redash/redash.3.0.0.b3134/redash/cli/init.py”, line 10, in
from redash.cli import users, groups, database, data_sources, organization
File “/opt/redash/redash.3.0.0.b3134/redash/cli/users.py”, line 10, in
from redash.handlers.users import invite_user
File “/opt/redash/redash.3.0.0.b3134/redash/handlers/init.py”, line 4, in
from redash.handlers.api import api
File “/opt/redash/redash.3.0.0.b3134/redash/handlers/api.py”, line 6, in
from redash.handlers.base import org_scoped_rule
File “/opt/redash/redash.3.0.0.b3134/redash/handlers/base.py”, line 8, in
from redash.authentication import current_org
File “/opt/redash/redash.3.0.0.b3134/redash/authentication/init.py”, line 11, in
from redash.authentication import google_oauth, saml_auth, remote_user_auth, ldap_auth
File “/opt/redash/redash.3.0.0.b3134/redash/authentication/saml_auth.py”, line 7, in
from saml2 import BINDING_HTTP_POST, BINDING_HTTP_REDIRECT, entity
File “/usr/local/lib/python2.7/dist-packages/saml2/entity.py”, line 7, in
from saml2.metadata import ENDPOINTS
File “/usr/local/lib/python2.7/dist-packages/saml2/metadata.py”, line 3, in
from saml2.sigver import security_context
File “/usr/local/lib/python2.7/dist-packages/saml2/sigver.py”, line 22, in
from saml2.cert import OpenSSLWrapper
File “/usr/local/lib/python2.7/dist-packages/saml2/cert.py”, line 7, in
from OpenSSL import crypto
File “/usr/local/lib/python2.7/dist-packages/OpenSSL/init.py”, line 8, in
from OpenSSL import rand, crypto, SSL
File “/usr/local/lib/python2.7/dist-packages/OpenSSL/SSL.py”, line 105, in
SSL_ST_INIT = _lib.SSL_ST_INIT
AttributeError: ‘module’ object has no attribute ‘SSL_ST_INIT’

You need to upgrade PyOpenSSL.
(It’s mentioned in the troubleshooting section in the upgrade guide)

Where can I see if I need to make a DB migration from v2 to v3? The release notes don’t say anything about that and the upgrade document is just a general advice document

You don’t. But regardless the upgrade script takes care of applying migrations.

@arikfr ok cool, that’s nice. Does this also work if I use the dockerimage from hub.docker.com? I couldn’t find something that would apply the migrations, if this is the dockerfile for that image https://github.com/getredash/redash/blob/master/Dockerfile

You need to run them manually. Our Docker entrypoint already supports run management commands. You need to run the manage db upgrade command. How depends on your setup though.