The downside here is that it would break downstream builds that set hadoop-3.2 if it's now called hadoop-3. That's not a huge deal. We can retain dummy profiles under the old names that do nothing, but that would be a quieter 'break'. I suppose this naming is only of importance to developers, who might realize that hadoop-3.2 means "hadoop-3.2 or later". And maybe the current naming leaves the possibility for a "hadoop-3.5" or something if that needed to be different.
I don't feel strongly but would default to leaving it, very slightly. On Thu, Jun 24, 2021 at 1:42 PM Chao Sun <sunc...@apache.org> wrote: > Hi, > > As Spark master has upgraded to Hadoop-3.3.1, the current Maven profile > name hadoop-3.2 is no longer accurate, and it may confuse Spark users when > they realize the actual version is not Hadoop 3.2.x. Therefore, I created > https://issues.apache.org/jira/browse/SPARK-33880 to change the profile > name to hadoop-3 and hadoop-2 respectively. What do you think? Is this > something worth doing as part of Spark 3.2.0 release? > > Best, > Chao >
