We just released the beta version of the V10 release . This contains many quality-of-life tweaks to the front-end (vertical navbar, session expiry wonât lose a userâs place in the app), improved visualisations (fixed table visualisation header, horizontal bar charts) and stability upgrades (typescript, Antd v4). For a full list of changes, we encourage you to checkout the CHANGELOG.
As always this release wouldnât be possible without the help of our community. This version had contributions from over 35 people
Our special thanks to Sohail Ahmed for disclosing a vulnerability in our âforgot passwordâ page which we patched in #5425.
Upgrading
(This section is duplicated from the previous release - since many users will upgrade directly from V8 â V10)
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:
Following that, force a recreation of your containers with docker-compose up --force-recreate --build and you should be good to go.
Gameplan
We plan for only a brief public beta so we can push new cloud images, documentation, and a setup script by the end of summer. Weâve been testing these changes internally for several months and the beta is quite stable. Thanks for your patience as this has been an off-kilter release cycle. We look forward to pushing a final release out ASAP.
Went from version 8 to 10 beta successfully. I have noted two things:
I seem to have a growing queued jobs anomaly. I did a docker-compose exec redis redis-cli flushall around 4pm est and by 9 pm I had 233 queued jobs. No scheduled queries. Note I did truncate the database tables for queries, dashboards, events, widgets, query results, and changes.
There will be, yes. But not pertaining to ES queries AFAIK.
I donât think anything has changed with the ES connector. Which isnât idea. The ES connector is in bad shape and we donât recommend anyone use it for production work Work was started on a new connector, but itâs blocked right now because we donât use ES internally and canât test it. If you can assist with the effort the PR is here: New Elasticsearch query runner by NicolasLM ¡ Pull Request #4391 ¡ getredash/redash ¡ GitHub
hello,
I upgraded to the v10.0.0-beta tag. The overall upgrade was smooth.
However - the features in CHANGELOG:
Feature: Added support for horizontal box plots
Feature: Added support for horizontal bar charts
I am not able to see box plots under chart type anymore(I know they showed up as deprecated in v8).
Also not able to see horizontal bar chart support. Any help is appreciated!
Follow-up question for V10, I hope someone can respond.
For V8, any user that belongs to a group that has full access to a data source was able to click on âedit Queryâ to view the query behind the data(for query that didnât belong to the same user, but to a different user in the same group) , but with V10, a user within the same group cant view other userâs queries.
Is there a workaround for this?
to add some context, the current group permission is :{create_dashboard,create_query,edit_dashboard,edit_query,view_query,view_source,execute_query,list_users,schedule_query,list_dashboards,list_alerts,list_data_sources}
hiďźcan i ask you how to update to 10.0.0-beta from 9.0.0-beta
i learn to build this version 9 just a moment
the note from 10.0.0 update note show that there are a couple extra modifications that need to be done in your docker-compose.ymlďźbut i use docker images show the tag is lastestďźand there is no tag informatiion in docker-compose.yml .
orz
whats else should edit for this updateďźcan you give me some help. pls
If I may clarify it accurately, by end of summer, youâd mean somewhere towards the end of August, or maybe around mid September. Kindly let me know if otherwise.