xushiyan commented on code in PR #7419: URL: https://github.com/apache/hudi/pull/7419#discussion_r1050932359
########## scripts/release/deploy_staging_jars.sh: ########## @@ -37,15 +37,26 @@ if [ "$#" -gt "1" ]; then fi declare -a ALL_VERSION_OPTS=( -"-Dscala-2.11 -Dspark2 -Dflink1.13" # for legacy bundle name -"-Dscala-2.12 -Dspark2 -Dflink1.13" # for legacy bundle name -"-Dscala-2.12 -Dspark3 -Dflink1.14" # for legacy bundle name -"-Dscala-2.11 -Dspark2.4 -Dflink1.13" -"-Dscala-2.11 -Dspark2.4 -Dflink1.14" -"-Dscala-2.12 -Dspark2.4 -Dflink1.13" -"-Dscala-2.12 -Dspark3.3 -Dflink1.15" -"-Dscala-2.12 -Dspark3.2 -Dflink1.14" -"-Dscala-2.12 -Dspark3.1 -Dflink1.14" # run this last to make sure utilities bundle has spark 3.1 +# upload all module jars and bundle jars +"-Dscala-2.11 -Dspark2.4" +"-Dscala-2.12 -Dspark2.4" +"-Dscala-2.12 -Dspark3.1" +"-Dscala-2.12 -Dspark3.2" +"-Dscala-2.12 -Dspark3.3" + +# spark bundles (legacy) (not overwriting previous uploads as these jar names are unique) +"-Dscala-2.11 -Dspark2 -pl packaging/hudi-spark-bundle" # for legacy bundle name hudi-spark-bundle_2.11 +"-Dscala-2.12 -Dspark2 -pl packaging/hudi-spark-bundle" # for legacy bundle name hudi-spark-bundle_2.12 +"-Dscala-2.12 -Dspark3 -pl packaging/hudi-spark-bundle" # for legacy bundle name hudi-spark3-bundle_2.12 + +# utilities bundles (legacy) (overwriting previous uploads) +"-Dscala-2.11 -Dspark2.4 -pl packaging/hudi-utilities-bundle" # utilities-bundle_2.11 is for spark 2.4 only +"-Dscala-2.12 -Dspark3.1 -pl packaging/hudi-utilities-bundle" # utilities-bundle_2.12 is for spark 3.1 only + +# flink bundles (overwriting previous uploads) +"-Dscala-2.12 -Dflink1.13 -Davro.version=1.10.0 -pl packaging/hudi-flink-bundle" +"-Dscala-2.12 -Dflink1.14 -Davro.version=1.10.0 -pl packaging/hudi-flink-bundle" +"-Dscala-2.12 -Dflink1.15 -Davro.version=1.10.0 -pl packaging/hudi-flink-bundle" Review Comment: unfortunately this is a short term workaround. Putting this in flink profiles under pom.xml will conflict with spark profiles, which interfere with current build commands used in azure CI, which takes much more efforts to resolve. Due to time constraint, overwriting the version from maven cmd is the shortest solution. -- 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]
