Upgrade OpenMetadata
Releases
The OpenMetadata community will be doing feature releases and stable releases.
- Feature releases are to upgrade your sandbox or POCs to give feedback to the community and any potential bugs that the community needs to fix.
- Stable releases are to upgrade your production environments and share it with your users.
Backup Metadata
Before upgrading your OpenMetadata version we recommend backing up the metadata.
The source of truth is stored in the underlying database (MySQL and Postgres supported). You can refer to the following guide for our backup utility:
Upgrade your installation
Once your metadata is safe, follow the required upgrade instructions:
Upgrade your Kubernetes installation
Upgrade a Docker DeploymentUpgrade your Docker installation
Upgrade a Bare Metal DeploymentUpgrade your Bare Metal installation
1.0 - Stable Release 🎉
OpenMetadata 1.0 is a stable release. Please check the release notes.
If you are upgrading production this is the recommended version to upgrade to.
Breaking Changes for 1.0 Stable Release
JWT Authentication Public Keys URL Change
With Release 1.0.0, JWT Authentication endpoint needs to be updated from {OPENMETADATA_HOST_NAME}/api/v1/config/jwks to {OPENMETADATA_HOST_NAME}/api/v1/system/config/jwks. This is required as part of API Endpoints. The Environment variable name is AUTHENTICATION_PUBLIC_KEYS. It expects list of URLs. One of the URL will be for OpenMetadata JWT Authentication Endpoint.
Airflow Configuration & Pipeline Service Client
The new section on the openmetadata.yaml configuration for the Pipeline Service Client has been updated.
We now have a pipelineServiceClientConfiguration, instead of the old airflowConfiguration.
Most existing environment variables remain the same, except for these three:
AIRFLOW_HOST_IP→PIPELINE_SERVICE_CLIENT_HOST_IPAIRFLOW_VERIFY_SSL→PIPELINE_SERVICE_CLIENT_VERIFY_SSLAIRFLOW_SSL_CERT_PATH→PIPELINE_SERVICE_CLIENT_SSL_CERT_PATH
When upgrading, make sure to update the environment variables and, if working on Bare Metal, make sure to use the updated openmetadata.yaml.
Deprecation Notice
- When configuring Bots, JWT tokens will be the preferred method of authentication. Any existing SSO-based service accounts will continue to work on 1.0, but will be fully deprecated on future releases.
- As we added the new Impala connector, We will remove the
impalascheme from Hive in the next release.
API Endpoint Changes
The following endpoints have been renamed in 1.0
| Previous Endpoint | New Endpoint |
|---|---|
api/v1 | Removed |
api/v1/services | Removed |
api/v1/version | api/v1/system/version |
api/v1/util/entities/count | api/v1/system/entities/count |
api/v1/util/services/count | api/v1/system/services/count |
api/v1/settings | api/v1/system/settings |
api/v1/config | api/v1/system/config |
api/v1/testSuite | api/v1/dataQuality/testSuites |
api/v1/testCase | api/v1/dataQuality/testCases |
api/v1/testDefinition | api/v1/dataQuality/testDefinitions |
api/v1/automations/workflow | api/v1/automations/workflows |
api/v1/events/subscription | api/v1/events/subscriptions |
api/v1/analytic/reportData | api/v1/analytics/dataInsights/data |
api/v1/analytics/webAnalyticEvent/ | api/v1/analytics/web/events/ |
api/v1/indexResource/reindex | api/v1/search/reindex |
api/v1/indexResource/reindex/status/{runMode} | api/v1/search/reindex/status/{runMode} |
Sample Data Deprecation
The SampleData service has been deprecated. It is now a CustomConnector. If you have some entities in SampleData, please DELETE the service if you don’t want to keep them, or we can help you migrate them to a Custom Connector.
Note that this service type was mostly used on quickstarts and tests to add some example assets into OpenMetadata. This should be transparent for most of the users.
Location Entity
We are deprecating the Location Entity in favor of the Containers and new Storage Service:
- Dropping the
location_entitytable, - Removing the
LocationAPIs.
If you did not have any custom implementation, this was partially used in the Glue Database connector. However, the information was not being actively shown.
If you had custom implementations on top of the Location APIs, reach out to us, and we can help migrate to the new Storage Services.
AWS Connectors
The endpointURL property is now formatted as a proper URI, e.g., http://something.com. If you have added this configuration in your connectors, please update the endpointURL format with the right scheme.
Note that this property is OPTIONAL, and for the most cases it will either be left blank or already configured with the right format for it to work properly, e.g., s3://....