mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-08-31 12:39:01 +00:00
MINOR: improve query log lineage docs (#16413)
This commit is contained in:
parent
eb88dc11c7
commit
cb8f4c612f
@ -33,13 +33,20 @@ A standard CSV should be comma separated, and each row represented as a single l
|
||||
{% /note %}
|
||||
|
||||
- **query_text:** This field contains the literal query that has been executed in the database. It is quite possible
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes `"<query>"` to not have any clashes
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes to not have any clashes
|
||||
with the comma as a separator.
|
||||
- **database_name (optional):** Enter the database name on which the query was executed.
|
||||
- **schema_name (optional):** Enter the schema name to which the query is associated.
|
||||
|
||||
Checkout a sample query log file [here](https://github.com/open-metadata/OpenMetadata/blob/main/ingestion/examples/sample_data/glue/query_log.csv).
|
||||
|
||||
```csv
|
||||
query_text,database_name,schema_name
|
||||
"select * from sales",default,information_schema
|
||||
"select * from marketing",default,information_schema
|
||||
"insert into marketing select * from sales",default,information_schema
|
||||
```
|
||||
|
||||
## Lineage Workflow
|
||||
In order to run a Lineage Workflow we need to make sure that Metadata Ingestion Workflow for corresponding service has already been executed. We will follow the steps to create a JSON configuration able to collect the query log file and execute the lineage workflow.
|
||||
|
||||
|
@ -34,8 +34,9 @@ A standard CSV should be comma separated, and each row represented as a single l
|
||||
{% /note %}
|
||||
|
||||
- **query_text:** This field contains the literal query that has been executed in the database. It is quite possible
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes `"<query>"` to not have any clashes
|
||||
with the comma as a separator.- **user_name (optional):** Enter the database user name which has executed this query.
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes to not have any clashes
|
||||
with the comma as a separator.
|
||||
- **user_name (optional):** Enter the database user name which has executed this query.
|
||||
- **start_time (optional):** Enter the query execution start time in YYYY-MM-DD HH:MM:SS format.
|
||||
- **end_time (optional):** Enter the query execution end time in YYYY-MM-DD HH:MM:SS format.
|
||||
- **aborted (optional):** This field accepts values as true or false and indicates whether the query was aborted during execution
|
||||
@ -44,6 +45,12 @@ A standard CSV should be comma separated, and each row represented as a single l
|
||||
|
||||
Checkout a sample query log file [here](https://github.com/open-metadata/OpenMetadata/blob/main/ingestion/examples/sample_data/glue/query_log.csv).
|
||||
|
||||
```csv
|
||||
query_text,database_name,schema_name
|
||||
"create table sales_analysis as select id, name from sales",default,information_schema
|
||||
"insert into marketing select * from sales",default,information_schema
|
||||
```
|
||||
|
||||
## Usage Workflow
|
||||
In order to run a Usage Workflow we need to make sure that Metadata Ingestion Workflow for corresponding service has already been executed. We will follow the steps to create a JSON configuration able to collect the query log file and execute the usage workflow.
|
||||
|
||||
|
@ -33,13 +33,20 @@ A standard CSV should be comma separated, and each row represented as a single l
|
||||
{% /note %}
|
||||
|
||||
- **query_text:** This field contains the literal query that has been executed in the database. It is quite possible
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes `"<query>"` to not have any clashes
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes to not have any clashes
|
||||
with the comma as a separator.
|
||||
- **database_name (optional):** Enter the database name on which the query was executed.
|
||||
- **schema_name (optional):** Enter the schema name to which the query is associated.
|
||||
|
||||
Checkout a sample query log file [here](https://github.com/open-metadata/OpenMetadata/blob/main/ingestion/examples/sample_data/glue/query_log.csv).
|
||||
|
||||
```csv
|
||||
query_text,database_name,schema_name
|
||||
"select * from sales",default,information_schema
|
||||
"select * from marketing",default,information_schema
|
||||
"insert into marketing select * from sales",default,information_schema
|
||||
```
|
||||
|
||||
## Lineage Workflow
|
||||
In order to run a Lineage Workflow we need to make sure that Metadata Ingestion Workflow for corresponding service has already been executed. We will follow the steps to create a JSON configuration able to collect the query log file and execute the lineage workflow.
|
||||
|
||||
|
@ -34,8 +34,9 @@ A standard CSV should be comma separated, and each row represented as a single l
|
||||
{% /note %}
|
||||
|
||||
- **query_text:** This field contains the literal query that has been executed in the database. It is quite possible
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes `"<query>"` to not have any clashes
|
||||
with the comma as a separator.- **user_name (optional):** Enter the database user name which has executed this query.
|
||||
that your query has commas `,` inside. Then, wrap each query in quotes to not have any clashes
|
||||
with the comma as a separator.
|
||||
- **user_name (optional):** Enter the database user name which has executed this query.
|
||||
- **start_time (optional):** Enter the query execution start time in YYYY-MM-DD HH:MM:SS format.
|
||||
- **end_time (optional):** Enter the query execution end time in YYYY-MM-DD HH:MM:SS format.
|
||||
- **aborted (optional):** This field accepts values as true or false and indicates whether the query was aborted during execution
|
||||
@ -44,6 +45,13 @@ A standard CSV should be comma separated, and each row represented as a single l
|
||||
|
||||
Checkout a sample query log file [here](https://github.com/open-metadata/OpenMetadata/blob/main/ingestion/examples/sample_data/glue/query_log.csv).
|
||||
|
||||
```csv
|
||||
query_text,database_name,schema_name
|
||||
"select * from sales",default,information_schema
|
||||
"select * from marketing",default,information_schema
|
||||
"insert into marketing select * from sales",default,information_schema
|
||||
```
|
||||
|
||||
## Usage Workflow
|
||||
In order to run a Usage Workflow we need to make sure that Metadata Ingestion Workflow for corresponding service has already been executed. We will follow the steps to create a JSON configuration able to collect the query log file and execute the usage workflow.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user