xushiyan commented on a change in pull request #4694: URL: https://github.com/apache/hudi/pull/4694#discussion_r793794668
########## File path: website/releases/release-0.10.1.md ########## @@ -0,0 +1,64 @@ +--- +title: "Release 0.10.1" +sidebar_position: 2 +layout: releases +toc: true +last_modified_at: 2022-01-26T22:07:00+08:00 +--- +# [Release 0.10.1](https://github.com/apache/hudi/releases/tag/release-0.10.1) ([docs](/docs/quick-start-guide)) + +## Migration Guide + +* This release (0.10.1) does not introduce any new table version, hence no migration needed if you are on 0.10.0. +* If migrating from an older release, please check the migration guide from the previous release notes, specifically the upgrade instructions in 0.6.0, 0.9.0 and 0.10.0. + +## Release Highlights + +### Explicit Spark 3 bundle names + +In the previous release (0.10.0), we added Spark 3.1.x support and made it the default Spark 3 version to build with. In 0.10.1, +we made the Spark 3 version explicit in the bundle name and published a new bundle for Spark 3.0.x. Specifically, these 2 bundles +are available in the public maven repository. + +* `hudi-spark3.1.2-bundle_2.12-0.10.1.jar` +* `hudi-spark3.0.3-bundle_2.12-0.10.1.jar` Review comment: @pan3793 hi thanks for the feedback. It does not indicate only exact versions are supported. The spark versions were [not stable across 3.0.x versions](https://spark.apache.org/docs/latest/sql-migration-guide.html#upgrading-from-spark-sql-301-to-302) that's why we wanted to be explicit for user to know the versions bundled with. As you suggested, with `major.minor` versions may suffice and looks like after spark 3.1 the APIs are more stable. In 0.11 we are dropping 3.0.x support and we can consider aligning on the names with just spark3.1 and spark3.2 in 0.11. cc @nsivabalan -- 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]
