Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

superset db upgrade not working when upgrading from v 0.35.2 to 1.0.1 #13272

Open
asdi744 opened this issue Feb 22, 2021 · 1 comment
Open

superset db upgrade not working when upgrading from v 0.35.2 to 1.0.1 #13272

asdi744 opened this issue Feb 22, 2021 · 1 comment
Labels

Comments

@asdi744
Copy link

@asdi744 asdi744 commented Feb 22, 2021

I am trying to upgrade superset from version 0.35.2 to 1.0.1

Expected results

superset db upgrade command should migrate my default db compatible to v 1.0.1

Actual results

superset db upgrade failed with the following error

sqlalchemy.exc.IntegrityError: (psycopg2.errors.NotNullViolation) column "table_name" contains null values

[SQL: ALTER TABLE tables ALTER COLUMN table_name SET NOT NULL]

Screenshots

Screenshot 2021-02-22 at 16 11 29

How to reproduce the bug

  1. pip install apache-superset
  2. superset db upgrade

Environment

(please complete the following information):

  • superset version: 1.0.1
  • python version: 3.7.3
  • flask version: 1.1.2
  • Werkzeug version 1.0.1

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.
@asdi744 asdi744 added the #bug label Feb 22, 2021
@asdi744
Copy link
Author

@asdi744 asdi744 commented Mar 10, 2021

Dear community, please help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant