Clearly state the command to execute via CLI for the profiling (#7708)

See https://openmetadata.slack.com/archives/C02B6955S4S/p1663439534423849?thread_ts=1663437719.374679&cid=C02B6955S4S for more context
This commit is contained in:
Marco Vito Moscaritolo 2022-09-25 19:37:02 +02:00 committed by GitHub
parent 98a3a1a173
commit ab947b93ea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -92,9 +92,9 @@ This setting allows you exclude or include specific column from the profiler. It
## YAML Configuration
In the [connectors](/openmetadata/connectors) section we showcase how to run the metadata ingestion from a JSON file using the Airflow SDK or the CLI via metadata ingest. Running a profiler workflow is also possible using a JSON configuration file.
In the [connectors](/openmetadata/connectors) section we showcase how to run the metadata ingestion from a JSON file using the Airflow SDK or the CLI via metadata ingest. Running a profiler workflow is also possible using a JSON configuration file.
This is a good option if you which to execute your workflow via the Airflow SDK or using the CLI. The serviceConnection config will be specific to your connector (you can find more information in the [connectors](/openmetadata/connectors) section), though the sourceConfig for the profiler will be similar across all connectors.
This is a good option if you which to execute your workflow via the Airflow SDK or using the CLI; if you use the CLI a profile workflow can be triggered with the command `metadata profile -c FILENAME.yaml`. The `serviceConnection` config will be specific to your connector (you can find more information in the [connectors](/openmetadata/connectors) section), though the sourceConfig for the profiler will be similar across all connectors.
```yaml
@ -115,4 +115,4 @@ This is a good option if you which to execute your workflow via the Airflow SDK
- orders
- customers
[...]
```
```