voonhous opened a new pull request, #19473:
URL: https://github.com/apache/hudi/pull/19473

   ### Describe the issue this Pull Request addresses
   
   Closes #19472.
   
   The AWS CloudWatchReporter section of the metrics page explains how to 
enable the reporter and supply
   credentials, but never says which artifact provides the reporter class. It 
ships in the optional
   `hudi-aws` module, which `packaging/hudi-spark-bundle/pom.xml` does not 
shade (`hudi-flink-bundle` and
   `hudi-kafka-connect-bundle` do), so a Spark user who follows the docs cannot 
load
   `org.apache.hudi.aws.metrics.cloudwatch.CloudWatchMetricsReporter` and has 
no way to know a second jar
   is needed.
   
   ### Summary and Changelog
   
   Adds one short paragraph to the AWS CloudWatchReporter section naming the 
`hudi-aws` module, the fact
   that not every engine bundle shades it, and the `hudi-aws-bundle` remedy.
   
   Applied to `website/docs/metrics.md` (next) and 
`website/versioned_docs/version-1.2.0/metrics.md`
   (the current released docs). The nine older versioned copies have the same 
gap and were left alone,
   per the usual next-plus-current convention -- happy to widen if preferred.
   
   ### Relationship to apache/hudi#19418
   
   Two halves of #15293. #19418 fixes the runtime failure, turning an 
unactionable `Unable to load class`
   into an error naming the missing class and the bundle to add. This one is 
prevention: a user who reads
   the docs first never reaches that error. The two are independent and can 
merge in either order.
   
   ### Impact
   
   Documentation only. No code, config, or behaviour change.
   
   ### Risk Level
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable
   - [x] CI passes on my PR
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to