yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2026-01-06 12:36:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Docs] - Oracle permissions explanation (#12755)

Browse Source 
* [Docs] - Oracle permissions explanation

* DAG generated configs docs
This commit is contained in:
Pere Miquel Brull 2023-08-07 11:04:01 +02:00 committed by GitHub
parent 6f89ca089d
commit e19d5fc397
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 39 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
openmetadata-docs/content/v1.1.1-SNAPSHOT/connectors/database/oracle/index.md
View File

@ -46,7 +46,6 @@ Configure and schedule Oracle metadata and profiler workflows from the OpenMetad
To ingest metadata from oracle user must have `CREATE SESSION` privilege for the user.
```sql
-- CREATE USER
CREATE USER user_name IDENTIFIED BY admin_password;
@ -58,9 +57,18 @@ GRANT new_role TO user_name;
-- GRANT CREATE SESSION PRIVILEGE TO USER
GRANT CREATE SESSION TO new_role;
```
With just these permissions, your user should be able to ingest the schemas, but not the tables inside them. To get
the tables, you should grant `SELECT` permissions to the tables you are interested in. E.g.,
```sql
SELECT ON ADMIN.EXAMPLE_TABLE TO new_role;
```
You can find further information [here](https://docs.oracle.com/javadb/10.8.3.0/ref/rrefsqljgrant.html). Note that
there is no routine out of the box in Oracle to grant SELECT to a full schema.
## Metadata Ingestion
{% partial

11
openmetadata-docs/content/v1.1.1-SNAPSHOT/connectors/database/oracle/yaml.md
View File

@ -52,7 +52,6 @@ To deploy OpenMetadata, check the Deployment guides.
To ingest metadata from oracle user must have `CREATE SESSION` privilege for the user.
```sql
-- CREATE USER
CREATE USER user_name IDENTIFIED BY admin_password;
@ -64,9 +63,17 @@ GRANT new_role TO user_name;
-- GRANT CREATE SESSION PRIVILEGE TO USER
GRANT CREATE SESSION TO new_role;
```
With just these permissions, your user should be able to ingest the schemas, but not the tables inside them. To get
the tables, you should grant `SELECT` permissions to the tables you are interested in. E.g.,
```sql
SELECT ON ADMIN.EXAMPLE_TABLE TO new_role;
```
You can find further information [here](https://docs.oracle.com/javadb/10.8.3.0/ref/rrefsqljgrant.html). Note that
there is no routine out of the box in Oracle to grant SELECT to a full schema.
### Python Requirements

20
openmetadata-docs/content/v1.1.1-SNAPSHOT/deployment/ingestion/openmetadata.md
View File

@ -164,6 +164,26 @@ A possible approach here is to update your `airflow.cfg` entries with:
auth_backends = airflow.api.auth.backend.basic_auth
```
#### DAG Generated Configs
Every time a DAG is created from OpenMetadata, it will also create a JSON file with some information about the
workflow that needs to be executed. By default, these files live under `${AIRFLOW_HOME}/dag_generated_configs`, which
in most environments translates to `/opt/airflow/dag_generated_configs`.
You can change this directory by specifying the environment variable `AIRFLOW__OPENMETADATA_AIRFLOW_APIS__DAG_GENERATED_CONFIGS`
or updating the `airflow.cfg` with:
```cfg
[openmetadata_airflow_apis]
dag_generated_configs=/opt/airflow/dag_generated_configs
```
A safe way to validate if the configuration is properly set in Airflow is to run:
```bash
airflow config get-value openmetadata_airflow_apis dag_generated_configs
```
### 4. Configure in the OpenMetadata Server
After installing the Airflow APIs, you will need to update your OpenMetadata Server.