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

   ### Change Logs
   
   Currently, there is no consistency for avro/parquet-avro dependecies in 
bundles. In some, they are included but not shaded (like hudi-gcp-bundle, 
hudi-hive-sync-bundle), while some have included and shaded both, and scopes 
are also not consistent. This PR ensures that these two dependecies are 
included and shaded in all bundles except hudi-timeline-server-bundle where 
these are not required at all.
   
   ### Impact
   
   _Describe any public API or user-facing feature change or any performance 
impact._
   
   **Risk level: low**
   
   No public API changes. But, we need to test different combination of bundles:
   * hudi-spark-bundle
   * hudi-utilities-bundle
   * hudi-hive-sync-bundle
   * hudi-datahub-sync-bundle
   * hudi-flink-bundle
   * hudispark-bundle + hudi-hive-sync-bundle
   * hudi-utilities-bundle + hudi-hive-sync-bundle
   * hudi-utilities-slim-bundle + hudi-hive-sync-bundle
   * hudi-aws-bundle + hudi-spark-bundle
   * hudi-gcp-bundle + hudi-spark-bundle
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change_
   
   - _The config description must be updated if new configs are added or the 
default value of the configs are changed_
   - _Any new feature or user-facing change requires updating the Hudi website. 
Please create a Jira ticket, attach the
     ticket number here and follow the 
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
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