2.1.0 release

[eschutho]

This is a discussion for feedback and testing of the 2.1.0 release candidates. The current RC is RC1.

The release candidate:
https://dist.apache.org/repos/dist/dev/superset/2.1.0rc1/

Git tag for the release:
https://github.com/apache/superset/tree/2.1.0rc1

The Change Log for the release:
https://github.com/apache/superset/blob/2.1.0rc1/CHANGELOG.md

The Updating instructions for the release:
https://github.com/apache/superset/blob/2.1.0rc1/UPDATING.md

Please vote for this release via the mailing list voting thread https://lists.apache.org/thread/cm63dzp5t0gg3x01qbm5rxz5pz2x2h6s

If you have any questions or feedback, you can post them here or in the #apache-releases slack channel. For discussions about bugs found, please post here as we will be keeping track of all bugs that need to go into any subsequent RCs from this list or the voting threads.

This is the full list of cherries that will be going on top of the 2.1 master cut: https://github.com/apache/superset/pulls?q=is%3Apr++label%3Av2.1+

[paulvanharen]

I found some issues installing 2.1.0rc1 destroying the 'out of the box' experience. Please find my findings at #23181.

[sfirke]

Under 2.1.0rc1 I am still experiencing the issue where on a tabbed dashboard with any filters out of scope on the first tab, the charts just spin and don't load. There are many issues for this bug, here's a discussion of it: #21263 (comment) I believe @codek confirmed this behavior in Slack.

[adimyth]

I am able to confirm that this issue persists. I tested out apache/superset:2.1.0rc1 docker image

Is the solution to #21263 a part of this release?

This is the one, I am looking forward to the most!

[eschutho]

Yes, all of the PRs that were created to fix the issue have been included in the 2.1 release. It looks like someone will need to submit a new PR for the fix.

[eschutho]

@lilykuang has volunteered to look into this issue

[sfirke]

This is solved in 2.1.0rc2 🙌

[sfirke]

There was a report on the dev listserve of a blank "Customize" tab on the Heatmap chart. I can reproduce with 2.1.0rc1, see below. But should there be any content on that Customize tab, or is the problem that the tab is included at all? On 2.0.1 Heatmap chart I don't see a Customize tab at all.

[eschutho]

@lilykuang has volunteered to look into this issue as well

[lilykuang]

fix for this #23243

[sfirke]

I've completed my testing. I reported two minor bugs that seem to be regressions in 2.1.0rc1: #23197 and #23220. They could probably be fixed in a 2.1.1 release IMO rather than holding up 2.1.0 if a fix is not currently available.

I added a note to anyone who can help debug the issue of some tabbed dashboards not loading when filters are out of scope: #20930 (comment) and I'm happy to discuss that further, screenshare my examples, and/or QA a possible fix.

[eschutho]

Thank you for this testing, @sfirke!

[eschutho]

@kgabryje made a quick fix for #23220: #23237

[sfirke]

thanks @kgabryje - that is a fast fix 😮 I'll plan to confirm the fix in 2.1.0rc2

[codek]

Fantastic! I'll also check rc2.

…

On Tue, 28 Feb 2023, 18:26 Sam Firke, ***@***.***> wrote: thanks @kgabryje <https://github.com/kgabryje> - that is a *fast* fix 😮 I'll plan to confirm the fix in 2.1.0rc2 — Reply to this email directly, view it on GitHub <#23164 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADY3OWF2JITYLXK2HIWADTWZY7LZANCNFSM6AAAAAAVE775NI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mdeshmu]

can this be included in 2.1.0rc2 ?

#23139

[eschutho]

Yes, just added, thank you.

[eschutho]

This was mentioned on slack: #23001

[zhaorui2022]

Is it possible to include #20448? I tried it locally using docker-compose and it has fixed an issue we encountered mentioned in #23289 It is a large commit and there were merge conflicts. I ended accepting everything in this commit and it seems working fine for me when using it locally.

[zhaorui2022]

by the way, when I say there were merge conflicts, my base was version 2.0.1.

[Samira-El]

Hi,
I wanted to test out the new feature introduced by this PR.

The doc says to add this:

from superset.reports.types import ReportScheduleExecutor
ALERT_REPORTS_EXECUTE_AS = [
    ReportScheduleExecutor.CREATOR_OWNER,
    ReportScheduleExecutor.CREATOR,
    ReportScheduleExecutor.MODIFIER_OWNER,
    ReportScheduleExecutor.MODIFIER,
    ReportScheduleExecutor.OWNER,
    ReportScheduleExecutor.SELENIUM,
]

But the enum ReportScheduleExecutor is no where to be found in the code.
It appears that this PR refactored the feature but the doc is outdated now.

[sfirke]

Looks like those docs just got updated in a PR today: #23323

[romankevich]

Is it possible to include this in 2.1.0 ?

• feat: Frontend tagging #20876
• feat: Add excel export #22006

[D3nn3]

Could we look into the following issue: #23218? I'd highly appreciate it 🙂

[codek]

Yay whoop! I'll try it out tomorrow.

…

On Tue, 14 Mar 2023, 18:44 Sam Firke, ***@***.***> wrote: This is solved in 2.1.0rc2 🙌 — Reply to this email directly, view it on GitHub <#23164 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADY3ORQT5E24OWTV3SNIZTW4C4ATANCNFSM6AAAAAAVE775NI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tranduydat]

Is drilldown feature supported in Apache Superset 2.1.0?

[mdeshmu]

Drill to Detail is available in 2.1.0. Drill By is yet to released.

[dat-linux]

Error: (sqlite3.OperationalError) no such table: ssh_tunnels
[SQL: SELECT ssh_tunnels.uuid AS ssh_tunnels_uuid, ssh_tunnels.created_on AS ssh_tunnels_created_on, ssh_tunnels.changed_on AS ssh_tunnels_changed_on, ssh_tunnels.extra_json AS ssh_tunnels_extra_json, ssh_tunnels.id AS ssh_tunnels_id, ssh_tunnels.database_id AS ssh_tunnels_database_id, ssh_tunnels.server_address AS ssh_tunnels_server_address, ssh_tunnels.server_port AS ssh_tunnels_server_port, ssh_tunnels.username AS ssh_tunnels_username, ssh_tunnels.password AS ssh_tunnels_password, ssh_tunnels.private_key AS ssh_tunnels_private_key, ssh_tunnels.private_key_password AS ssh_tunnels_private_key_password, ssh_tunnels.created_by_fk AS ssh_tunnels_created_by_fk, ssh_tunnels.changed_by_fk AS ssh_tunnels_changed_by_fk
FROM ssh_tunnels
WHERE ssh_tunnels.database_id = ?]
[parameters: (1,)]
(Background on this error at: https://sqlalche.me/e/14/e3q8)

[mdeshmu]

Seems like missing table for recently added ssh tunnels support for database connections. Can you perform “superset db upgrade” and see if that solves the problem.

[sandeeppennant]

I have the same issue, even after the superset db upgrade the issue remain's same.
Your suggestions/help is much appreciated

[sandeeppennant]

Seems like missing table for recently added ssh tunnels support for database connections. Can you perform “superset db upgrade” and see if that solves the problem.

I have the same issue, even after the superset db upgrade the issue remain's same.
Your suggestions/help is much appreciated

[LeoDiep]

Hi, is the 2.1.0 update this freezing column function for pivot table. This would be massive useful for users when checking large tables or for who having small screen.
#8238

[Gurbrinder0031]

Hi. in 2.1.0 '{{ from_dttm }}' is not working in dataset showing same in response and same for current user id.

[Gurbrinder0031]

Saved and Discard buttons are not showing in apache superset2.1.0