steveloughran commented on PR #8094: URL: https://github.com/apache/hadoop/pull/8094#issuecomment-3574897460
> How does it affect hadoop classpath? As far as I know, many downstream projects require adding the output of hadoop classpath to their classpath. * does nothing for maven/gradle imports of hadoop-cloud-storage * if you add hadoop/common/* and hadoop/commmon/lib/* to your CP you may now get more cloud connectors > I suppose it has no effect on hadoop-client-* jars, right? correct > Which maven profiles will be enabled by the Apache binary release? in other words, how to reproduce it from the source release locally? It doesn't set any of the new profiles, meaning the hadoop-* jars will be there, abfs will work (limited dependendencies) but anything else needs extra jars added. FWIW third-party cloud deployments (EMR, azure etc) all get their connectors onto the classpath, somehow. And because hadoop-aws has a bit of bash script in its src/main, somehow it gets into "bin/hadoop fs" commands...the shell script wiring up logic does this. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
