Skip to content
This repository was archived by the owner on Oct 4, 2024. It is now read-only.

Deployment in a new VPC gives version 0.999.0dev and not 1.4.0 #32

Open
nazbadat opened this issue Jan 7, 2022 · 5 comments
Open

Deployment in a new VPC gives version 0.999.0dev and not 1.4.0 #32

nazbadat opened this issue Jan 7, 2022 · 5 comments

Comments

@nazbadat
Copy link

nazbadat commented Jan 7, 2022

Hi there,

Is there a way to upgrade superset after deploying via CloudFormation? I notice that the CF template to deploy to an existing VPC notes that the platform version should be 1.4.0, but the new VPC template file has no reference to a version being used. We want to upgrade to the latest version as there is no BigQuery database connection types included. Any clarification on this would be greatly appreciated!

Thanks
Naz

Screenshot 2022-01-07 at 14 09 25

@rainerledesma
Copy link

Same question here. @nazbadat where you able to figure out how to do so?

@yike5460
Copy link
Contributor

Hi, the upstream sync up in on going, and I assume BigQuery support is what you need I such release?

@nazbadat
Copy link
Author

@yike5460 Yes that is correct. @rainerledesma Unfortunately due to business needs of the tool, I cloned the repository and ran it locally using docker-compose, then added the necessary config to superset-config.py and it worked as expected. The version number still didn't change, but BigQuery was functional.

@yike5460
Copy link
Contributor

1.4 is not mandatory for BigQuery, the dependency you need to install is https://github.com/googleapis/python-bigquery-sqlalchemy, with command
pip install sqlalchemy-bigquery

@yike5460
Copy link
Contributor

@nazbadat v1.4.1 is now merged in official solution, kindly let me know your further feedback.
image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants