Thanks all for the feedback! Yes I agree that we should target this for
Apache Spark 3.3 release. I'll put this aside for now and pick it up again
after the 3.2 release is finished.
> And maybe the current naming leaves the possibility for a "hadoop-3.5" or
something if that needed to be
+1 for targeting the renaming for Apache Spark 3.3 at the current phase.
On Fri, Jun 25, 2021 at 6:55 AM DB Tsai wrote:
> +1 on renaming.
>
> DB Tsai | https://www.dbtsai.com/ | PGP 42E5B25A8F7A82C1
>
> On Jun 24, 2021, at 11:41 AM, Chao Sun wrote:
>
> Hi,
>
> As Spark master has upgraded
+1 on renaming.
DB Tsai | https://www.dbtsai.com/ | PGP 42E5B25A8F7A82C1
> On Jun 24, 2021, at 11:41 AM, Chao Sun 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
For renaming, I'd target it for Apache Spark 3.3 instead of Apache Spark 3.2
because this is the first release of using Apache Hadoop 3.3.1 and we may
need to revert Apache Hadoop 3.3.1 during RC period.
Dongjoon.
On Thu, Jun 24, 2021 at 12:24 PM Sean Owen wrote:
> The downside here is that it
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
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
