Skip to content
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.

Sign up for GitHub

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

FIXED - [docs] profiler image for column #14443

Merged
merged 1 commit into from
Dec 19, 2023
Merged

FIXED - [docs] profiler image for column #14443

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions openmetadata-docs/content/v1.2.x/connectors/ingestion/workflows/profiler/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ This Pipeline will be in charge of feeding the Profiler tab of the Table Entity,


{% image
src="/images/v1.2/features/ingestion/workflows/profiler/profiler-summary-colomn.png"
src="/images/v1.2/features/ingestion/workflows/profiler/profiler-summary-column.png"
alt="Column profile summary page"
caption="Column profile summary page"
/%}
Expand Down Expand Up @@ -389,4 +389,4 @@ By default, the profiler will compute all the metrics against all the columns. T
For example, excluding `id` columns will reduce the number of columns against which the metrics are computed.

### 4. Set Up Multiple Workflow
If you have a large number of tables you would like to profile, setting up multiple workflows will help distribute the load. It is important though to monitor your instance CPU, and memory as having a large amount of workflow running simultaneously will require an adapted amount of resources.
If you have a large number of tables you would like to profile, setting up multiple workflows will help distribute the load. It is important though to monitor your instance CPU, and memory as having a large amount of workflow running simultaneously will require an adapted amount of resources.
Loading