yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-08-22 16:08:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add Database Connection Environment Variables docs (#7350)

Browse Source
This commit is contained in:
Akash Jain 2022-09-09 02:43:41 +05:30 committed by GitHub
parent f2fc45ea41
commit 991344ddfa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
View File

@ -5,11 +5,15 @@ slug: /deployment/upgrade/versions/011-to-012
# Upgrade from 0.11 to 0.12 # Upgrade from 0.11 to 0.12
Upgrading from 0.11 to 0.12 can be done directly on your instances. This page will list a couple of details that you Upgrading from 0.11 to 0.12 can be done directly on your instances. This page will list a couple of details that you should take into consideration when running the upgrade.
should take into consideration when running the upgrade.
## Highlights ## Highlights
### Database Connection Environment Variables
On 0.11, the Environment Variables to connect to Database used were MYSQL_USER, MYSQL_USER_PASSWORD, MYSQL_HOST, MYSQL_PORT, MYSQL_DATABASE. These environment variables are changed in 0.12 Release with DB_USER, DB_USER_PASSWORD, DB_HOST, DB_PORT, OM_DATABASE. This will effect to all the bare metal and docker instances which configures a custom database depending on the above environment variable values.
This change is however not affected for Kubernetes deployments.
### Data Profiler and Data Quality Tests ### Data Profiler and Data Quality Tests
On 0.11, the Profiler Workflow handled two things: On 0.11, the Profiler Workflow handled two things: