[
https://issues.apache.org/jira/browse/HUDI-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Xu updated HUDI-4052:
-----------------------------
Labels: pull-request-available (was: client pull-request-available
third-party)
> Move AWS Cloudwatch metric configs to hudi-client-common instead of hudi-aws
> ----------------------------------------------------------------------------
>
> Key: HUDI-4052
> URL: https://issues.apache.org/jira/browse/HUDI-4052
> Project: Apache Hudi
> Issue Type: Task
> Reporter: Sagar Sumit
> Assignee: Sagar Sumit
> Priority: Critical
> Labels: pull-request-available
> Fix For: 0.11.1
>
>
> Currently, HoodieMetricsCloudWatchConfig is part of hudi-aws module, while
> HoodieMetricConfig is part of hudi-client-common. The builder of
> HoodieMetricConfig uses HoodieMetricsCloudWatchConfig. When we want to use
> hudi write client in other engines (presto/trino), we need to include
> hudi-aws module because HoodieMetricsConfig initialization falls in that
> path. But, this bloats the presto/trino bundle, which we want to keep as
> light as possible.
> We should try to decouple the two. Let all metric configs be in client-common
> (e.g. prometheus and datadog configs are already there). This way we can
> exclude hudi-aws from the bundles.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
