-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Improvements for database setup docs #13696
Conversation
|
||
The exact format description is described in the SQLAlchemy documentation, see `Database Urls <https://docs.sqlalchemy.org/en/14/core/engines.html>`__. We will also show you some examples below. | ||
|
||
Set up a MySQL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Set up a MySQL | |
Set up MySQL |
or
Set up a MySQL | |
Setting up a MySQL Database |
Set up a PostgreSQL | ||
------------------- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Set up a PostgreSQL | |
------------------- | |
Set up a PostgreSQL Database | |
----------------------------- |
or
Set up a PostgreSQL | |
------------------- | |
Set up PostgreSQL | |
----------------------------- |
CREATE USER airflow_user WITH PASSWORD 'airflow_user'; | ||
GRANT ALL PRIVILEGES ON DATABASE airflow_db TO airflow_user; | ||
|
||
You need to create a database and a user that Airflow will use to access this database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to create a database and a user that Airflow will use to access this database. |
already mentioned before the code-block
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor changes suggested or else LGTM
The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest master or amend the last commit of the PR, and push it with --force-with-lease. |
(cherry picked from commit 8080929)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.