-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Increase size of column name
in table ab_view_meu
#6532
Increase size of column name
in table ab_view_meu
#6532
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6532 +/- ##
=========================================
+ Coverage 73.5% 73.5% +<.01%
=========================================
Files 72 72
Lines 10001 10002 +1
=========================================
+ Hits 7351 7352 +1
Misses 2650 2650
Continue to review full report at Codecov.
|
Ping @mistercrunch |
LGTM |
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
@betodealmeida when I do |
@aboganas I also had problems when deploying this, but it eventually went through after I killed some processes in MySQL. I assumed in my case it was taking too long because of the size of the table. I tested on a clean install and it works fine. @mistercrunch any idea why this could be hanging? |
There's another script that runs a similar command (https://github.com/apache/incubator-superset/blob/46c86672c8320c0003c2eb26f73db6daa2767996/superset/migrations/versions/956a063c52b3_adjusting_key_length.py#L18). |
I left it running and it went through after like 8 hours. so maybe as you said there was a process holding it up |
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
* Create migration script * Use batch operation for ALTER COLUMN (cherry picked from commit e2b9625)
#5915 introduced support for Google Spreadsheets as datasources, using the
gsheetsdb
module. The code was tested using only SQLite as Superset's database. Today I discovered it fails in MySQL (and probably other databases that enforce column sizes for strings), since the table name of a Google spreadsheet is too big to be stored in theab_view_menu
table.I increased the size of the column
name
from 100 to 255 characters, and tested the Google connector using MySQL as the main database for Superset.