Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
3.3.4
-
None
-
None
Description
The hadoop-yarn-applications-mawo-core module will currently publish a file with extension bin.tar.gz during the maven deploy step: https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-mawo/hadoop-yarn-applications-mawo-core/src/assembly/bin.xml#L16.
I don't know whether the community considers this to be a bug or not, but creating a ticket because the deploy step typically creates JAR and POM files, and some maven repositories that are intended to only host JARs will have allowlists of file extensions that block tarballs from being published, and therefore cause the maven deploy operation to fail with this error:
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://<hostname>/artifactory/<repo_name>/org/apache/hadoop/applications/mawo/hadoop-yarn-applications-mawo-core/<version>/hadoop-yarn-applications-mawo-core-<version>-bin.tar.gz. Return code is: 409, ReasonPhrase: .
Feel free to close if the community doesn't consider this to be a problem, but notably it is a regression from versions predating mawo when only JAR and POM files were published in the deploy step.