pt
/
superset
mirror of https://github.com/apache/superset.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
superset/UPDATING.md

61 lines
3.0 KiB
Markdown
Raw Normal View History

[security] Refactor security code into SupersetSecurityManager (#4565) * move access permissions methods to security manager * consolidate all security methods into SupersetSecurityManager * update security method calls * update calls from tests * move get_or_create_main_db to utils * raise if supersetsecuritymanager is not extended * rename sm to security_manager
2018-03-27 19:46:02 -04:00
# Updating Superset
This file documents any backwards-incompatible changes in Superset and
assists people when migrating to a new version.
UPDATING.md entry about dashboard v2 forced migration in 0.28
2018-08-27 21:01:20 -04:00
## Superset 0.28.0
Deprecate support for Python < 3.6 (#5985) * Deprecate support for Python < 3.6 This is a first step, beyond this we can: * remove all from future imports * remove 'six' lib as a dependency * start using f-strings * enjoy ourselves * fix tox * Rebasing * fix
2018-10-05 13:44:45 -04:00
* Support for Python 2 is deprecated, we only support >=3.6 from
`0.28.0` onwards
UPDATING.md entry about dashboard v2 forced migration in 0.28
2018-08-27 21:01:20 -04:00
* Superset 0.28 deprecates the previous dashboard layout. While 0.27
offered a migration workflow to users and allowed them to validate and
publish their migrated dashboards individually, 0.28 forces
the migration of all
dashboards through an automated db migration script. We
do recommend that you take a backup prior to this migration.
[refactor] Remove dependency on personal fork of supercluster from mapbox visualizations (#5902) * [refactor] Remove dependency to personal fork of supercluster from mapbox visualizations - Update dependency to reference the vanilla supercluster - Clean up backend api call for mapbox vizzes to ensure a boolean is sent to indicate whether the viz includes custom metric for clustering - Refactor of mapbox and its cluster overlay components to use vanilla supercluster and its recommeded way for handling clustering based on custom aggregations. - Allow reclustering within the initial bounds on render in mapbox visualizations (stay true to old behaviors). - Remove the median aggregation from available cluster label aggregators as there is no memory efficient way to implement this and it is unknown how often this feature is used - Updating doc to mention the backward incompatible change re median * Perform the check for has_custom_metric through `not None` to produce a boolean and rename the field reflect it is a boolean.
2018-09-18 15:38:17 -04:00
* Superset 0.28 deprecates the `median` cluster label aggregator for mapbox visualizations. This particular aggregation is not supported on mapbox visualizations going forward.
Migrate dashboard positions data from v1 to v2 format (#5463) * Migrate dashboard positions data from v1 to v2 format * UPDATING.md * rebase onto master
2018-07-24 18:14:11 -04:00
## Superset 0.27.0
[refactor] Remove dependency on personal fork of supercluster from mapbox visualizations (#5902) * [refactor] Remove dependency to personal fork of supercluster from mapbox visualizations - Update dependency to reference the vanilla supercluster - Clean up backend api call for mapbox vizzes to ensure a boolean is sent to indicate whether the viz includes custom metric for clustering - Refactor of mapbox and its cluster overlay components to use vanilla supercluster and its recommeded way for handling clustering based on custom aggregations. - Allow reclustering within the initial bounds on render in mapbox visualizations (stay true to old behaviors). - Remove the median aggregation from available cluster label aggregators as there is no memory efficient way to implement this and it is unknown how often this feature is used - Updating doc to mention the backward incompatible change re median * Perform the check for has_custom_metric through `not None` to produce a boolean and rename the field reflect it is a boolean.
2018-09-18 15:38:17 -04:00
* Superset 0.27 start to use nested layout for dashboard builder, which is not
Migrate dashboard positions data from v1 to v2 format (#5463) * Migrate dashboard positions data from v1 to v2 format * UPDATING.md * rebase onto master
2018-07-24 18:14:11 -04:00
backward-compatible with earlier dashboard grid data. We provide migration script
[refactor] Remove dependency on personal fork of supercluster from mapbox visualizations (#5902) * [refactor] Remove dependency to personal fork of supercluster from mapbox visualizations - Update dependency to reference the vanilla supercluster - Clean up backend api call for mapbox vizzes to ensure a boolean is sent to indicate whether the viz includes custom metric for clustering - Refactor of mapbox and its cluster overlay components to use vanilla supercluster and its recommeded way for handling clustering based on custom aggregations. - Allow reclustering within the initial bounds on render in mapbox visualizations (stay true to old behaviors). - Remove the median aggregation from available cluster label aggregators as there is no memory efficient way to implement this and it is unknown how often this feature is used - Updating doc to mention the backward incompatible change re median * Perform the check for has_custom_metric through `not None` to produce a boolean and rename the field reflect it is a boolean.
2018-09-18 15:38:17 -04:00
to automatically convert dashboard grid to nested layout data. To be safe, please
take a database backup prior to this upgrade. It's the only way people could go
Migrate dashboard positions data from v1 to v2 format (#5463) * Migrate dashboard positions data from v1 to v2 format * UPDATING.md * rebase onto master
2018-07-24 18:14:11 -04:00
back to a previous state.
Bump celery to 4.1.1 (#5134) * Bump celery to 4.1.1 Docs reference `celery worker --app=superset.sql_lab:celery_app --pool=gevent -Ofair` command which seems only to work with Celery 4.1.1 * Add UPDATING.md message
2018-06-04 17:54:36 -04:00
## Superset 0.26.0
* Superset 0.26.0 deprecates the `superset worker` CLI, which is a simple
wrapper around the `celery worker` command, forcing you into crafting
your own native `celery worker` command. Your command should look something
like `celery worker --app=superset.sql_lab:celery_app --pool=gevent -Ofair`
Add note about 0.25.0 upgrade in UPDATING.md (#4883)
2018-04-30 12:47:48 -04:00
## Superset 0.25.0
CHANGELOG for 0.25.0 (#4948)
2018-05-08 11:24:54 -04:00
Superset 0.25.0 contains a backwards incompatible changes.
Add note about 0.25.0 upgrade in UPDATING.md (#4883)
2018-04-30 12:47:48 -04:00
If you run a production system you should schedule downtime for this
upgrade.
CHANGELOG for 0.25.0 (#4948)
2018-05-08 11:24:54 -04:00
The PRs bellow have more information around the breaking changes:
* [4587](https://github.com/apache/incubator-superset/pull/4587) : a backward
incompatible database migration that requires downtime. Once the
db migration succeeds, the web server needs to be restarted with the
new version. The previous version will fail
* [4565](https://github.com/apache/incubator-superset/pull/4565) : we've
changed the security model a bit where in the past you would have to
define your authentication scheme by inheriting from Flask
[refactor] Remove dependency on personal fork of supercluster from mapbox visualizations (#5902) * [refactor] Remove dependency to personal fork of supercluster from mapbox visualizations - Update dependency to reference the vanilla supercluster - Clean up backend api call for mapbox vizzes to ensure a boolean is sent to indicate whether the viz includes custom metric for clustering - Refactor of mapbox and its cluster overlay components to use vanilla supercluster and its recommeded way for handling clustering based on custom aggregations. - Allow reclustering within the initial bounds on render in mapbox visualizations (stay true to old behaviors). - Remove the median aggregation from available cluster label aggregators as there is no memory efficient way to implement this and it is unknown how often this feature is used - Updating doc to mention the backward incompatible change re median * Perform the check for has_custom_metric through `not None` to produce a boolean and rename the field reflect it is a boolean.
2018-09-18 15:38:17 -04:00
App Builder's
CHANGELOG for 0.25.0 (#4948)
2018-05-08 11:24:54 -04:00
`from flask_appbuilder.security.sqla.manager import SecurityManager`,
you now have to derive Superset's
own derivative `superset.security.SupersetSecurityManager`. This
can provide you with more hooks to define your own logic and/or defer
permissions to another system as needed. For all implementation, you
simply have to import and derive `SupersetSecurityManager` in place
of the `SecurityManager`
[refactor] Remove dependency on personal fork of supercluster from mapbox visualizations (#5902) * [refactor] Remove dependency to personal fork of supercluster from mapbox visualizations - Update dependency to reference the vanilla supercluster - Clean up backend api call for mapbox vizzes to ensure a boolean is sent to indicate whether the viz includes custom metric for clustering - Refactor of mapbox and its cluster overlay components to use vanilla supercluster and its recommeded way for handling clustering based on custom aggregations. - Allow reclustering within the initial bounds on render in mapbox visualizations (stay true to old behaviors). - Remove the median aggregation from available cluster label aggregators as there is no memory efficient way to implement this and it is unknown how often this feature is used - Updating doc to mention the backward incompatible change re median * Perform the check for has_custom_metric through `not None` to produce a boolean and rename the field reflect it is a boolean.
2018-09-18 15:38:17 -04:00
* [4835](https://github.com/apache/incubator-superset/pull/4835) :
CHANGELOG for 0.25.0 (#4948)
2018-05-08 11:24:54 -04:00
our `setup.py` now only pins versions where required, giving you
more latitude in using versions of libraries as needed. We do now
provide a `requirements.txt` with pinned versions if you want to run
the suggested versions that `Superset` builds and runs tests against.
Simply `pip install -r requirements.txt` in your build pipeline, likely
prior to `pip install superset==0.25.0`