Re: [VOTE] Hadoop 3.2.x EOL

2023-12-05 Thread Mingliang Liu 
+1

On Tue, Dec 5, 2023 at 8:09 PM Xiaoqiao He  wrote:

> Dear Hadoop devs,
>
> Given the feedback from the discussion thread [1], I'd like to start
> an official thread for the community to vote on release line 3.2 EOL.
>
> It will include,
> a. An official announcement informs no further regular Hadoop 3.2.x
> releases.
> b. Issues which target 3.2.5 will not be fixed.
>
> This vote will run for 7 days and conclude by Dec 13, 2023.
>
> I’ll start with my +1.
>
> Best Regards,
> - He Xiaoqiao
>
> [1] https://lists.apache.org/thread/bbf546c6jz0og3xcl9l3qfjo93b65szr
>

Apache Hadoop qbt Report: trunk+JDK11 on Linux/x86_64

2023-12-05 Thread Apache Jenkins Server 
For more details, see 
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/593/

[Dec 3, 2023, 9:39:55 AM] (github) HDFS-17260. Fix the logic for reconfigure 
slow peer enable for Namenode. (#6279). Contributed by huangzhaobo99.
[Dec 3, 2023, 10:36:20 AM] (github) YARN-11561. [Federation] GPG Supports 
Format PolicyStateStore. (#6300) Contributed by Shilun Fan.
[Dec 4, 2023, 1:16:38 PM] (github) HDFS-17218. NameNode should process time out 
excess redundancy blocks (#6176). Contributed by Haiyang Hu.
[Dec 4, 2023, 1:19:33 PM] (github) HDFS-17250. 
EditLogTailer#triggerActiveLogRoll should handle thread Interrupted (#6266). 
Contributed by Haiyang Hu.

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Hadoop 3.2.x EOL

2023-12-05 Thread Ayush Saxena 
+1

-Ayush

> On 06-Dec-2023, at 9:40 AM, Xiaoqiao He  wrote:
> 
> Dear Hadoop devs,
> 
> Given the feedback from the discussion thread [1], I'd like to start
> an official thread for the community to vote on release line 3.2 EOL.
> 
> It will include,
> a. An official announcement informs no further regular Hadoop 3.2.x
> releases.
> b. Issues which target 3.2.5 will not be fixed.
> 
> This vote will run for 7 days and conclude by Dec 13, 2023.
> 
> I’ll start with my +1.
> 
> Best Regards,
> - He Xiaoqiao
> 
> [1] https://lists.apache.org/thread/bbf546c6jz0og3xcl9l3qfjo93b65szr

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[VOTE] Hadoop 3.2.x EOL

2023-12-05 Thread Xiaoqiao He 
Dear Hadoop devs,

Given the feedback from the discussion thread [1], I'd like to start
an official thread for the community to vote on release line 3.2 EOL.

It will include,
a. An official announcement informs no further regular Hadoop 3.2.x
releases.
b. Issues which target 3.2.5 will not be fixed.

This vote will run for 7 days and conclude by Dec 13, 2023.

I’ll start with my +1.

Best Regards,
- He Xiaoqiao

[1] https://lists.apache.org/thread/bbf546c6jz0og3xcl9l3qfjo93b65szr

Re: [DISCUSS] Make some release lines EOL

2023-12-05 Thread Xiaoqiao He 
Thanks all for your feedback, I will start an official vote thread.

Best Regards,
- He Xiaoqiao


On Tue, Dec 5, 2023 at 11:23 PM Masatake Iwasaki 
wrote:

> +1 on marking 3.2 EOL.
>
> For branch-2.10, just keeping cherry-picking critical our CVEs without
> release sounds good.
> If someone really want, I can try to put 2.10.3 up.
> dev-support/bin/create-release looks still working with some trivial fixes.
>
> On Tue, Dec 5, 2023 at 7:45 PM Steve Loughran
>  wrote:
> >
> > +1 for making 3.3 and 3.4 the maintained lines
> >
> > 3.2.x we should say -as it is true- that the age of the dependencies is
> > such that it is transitively insecure. To fix those, people must upgrade.
> >
> > For 2.10.x, we should think about whether to cherrypick our own CVEs
> there,
> > but not actually do any new ASF releases.
> > I couldn't even get hold of a java7 JDK to do the release even if I
> wanted
> > to -the same must hold for many others; getting a new release qualified
> > would be hard. Best to say "upgrade time'.
> >
> >
> > This goes well with a 3.4.0 release, as there's a clear story: we have a
> > new 3.4.x line stabilising, if you want something already stable move
> onto
> > 3.3.x if you hadn't already
> >
> >
> >
> >
> >
> > On Mon, 4 Dec 2023 at 12:39, Xiaoqiao He  wrote:
> >
> > > Hi folks,
> > >
> > > There are many discussions about which release lines should we still
> > > consider actively
> > > maintained in history. I want to launch this topic again, and try to
> get a
> > > consensus.
> > >
> > > From download page[1] and active branches page[2], we have the
> following
> > > release lines:
> > > Hadoop 3.3 Release (release-3.3.5 at Jun 22 2022),  360 commits
> checked in
> > > since last release.
> > > Hadoop 3.2 Release (release-3.2.4 at Jul 11, 2022) 36 commits checked
> in
> > > since last release.
> > > Hadoop 2.10 Release (release-2.10.2 at May 17, 2022) 24 commits
> checked in
> > > since last release.
> > >
> > > And Hadoop 3.4.0 will be coming soon which Shilun Fan (maybe
> cooperating
> > > with Ahmar Suhail?)
> > > has been actively working on getting the 3.4.0 release out.
> > >
> > > Considering the less updates for some active branches, should we
> declare to
> > > our downstream
> > > users that some of these lines will EOL?
> > >
> > > IMO we should announce EOL branch-2.10 and branch-3.2 which are not
> active
> > > now.
> > > Then we could focus on minor active branches (branch-3.3 and
> branch-3.4)
> > > and increase release pace.
> > >
> > > So how about to keep branch-3.3 and branch-3.4 release lines as
> actively
> > > maintained, And mark branch-2.10 and branch-3.2 EOL? Any opinions?
> Thanks.
> > >
> > > Best Regards,
> > > - He Xiaoqiao
> > >
> > > [1] https://hadoop.apache.org/releases.html
> > > [2]
> > >
> > >
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Active+Release+Lines
> > >
>
> -
> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>
>

Re: [DISCUSS] Make some release lines EOL

2023-12-05 Thread slfan1989 
+1 on marking 3.2 EOL.

+1 just keeping cherry-picking critical our CVEs without release on
branch-2.10.

+1 The new version is released based on version 3.4.0.

I am willing to take on the work during the release of the new version and
look forward to a smooth release.

Best Regards,
Shilun Fan.

Original

From:"Masatake Iwasaki"< >;

Date:2023/12/5 23:21

To:"Hadoop Common"< common-dev@hadoop.apache.org >;"Hdfs-dev"<
hdfs-...@hadoop.apache.org >;"yarn-dev"< yarn-...@hadoop.apache.org >;
"mapreduce-dev"< mapreduce-...@hadoop.apache.org >;"<
priv...@hadoop.apache.org>"< priv...@hadoop.apache.org >;

Subject:Re: [DISCUSS] Make some release lines EOL

+1 on marking 3.2 EOL.

For branch-2.10, just keeping cherry-picking critical our CVEs without
release sounds good.
If someone really want, I can try to put 2.10.3 up.
dev-support/bin/create-release looks still working with some trivial fixes.

On Tue, Dec 5, 2023 at 7:45 PM Steve Loughran
wrote:
>
> +1 for making 3.3 and 3.4 the maintained lines
>
> 3.2.x we should say -as it is true- that the age of the dependencies is
> such that it is transitively insecure. To fix those, people must upgrade.
>
> For 2.10.x, we should think about whether to cherrypick our own CVEs
there,
> but not actually do any new ASF releases.
> I couldn't even get hold of a java7 JDK to do the release even if I wanted
> to -the same must hold for many others; getting a new release qualified
> would be hard. Best to say "upgrade time'.
>
>
> This goes well with a 3.4.0 release, as there's a clear story: we have a
> new 3.4.x line stabilising, if you want something already stable move onto
> 3.3.x if you hadn't already
>
>
>
>
>
> On Mon, 4 Dec 2023 at 12:39, Xiaoqiao He wrote:
>
> > Hi folks,
> >
> > There are many discussions about which release lines should we still
> > consider actively
> > maintained in history. I want to launch this topic again, and try to
get a
> > consensus.
> >
> > From download page[1] and active branches page[2], we have the following
> > release lines:
> > Hadoop 3.3 Release (release-3.3.5 at Jun 22 2022), 360 commits checked
in
> > since last release.
> > Hadoop 3.2 Release (release-3.2.4 at Jul 11, 2022) 36 commits checked in
> > since last release.
> > Hadoop 2.10 Release (release-2.10.2 at May 17, 2022) 24 commits checked
in
> > since last release.
> >
> > And Hadoop 3.4.0 will be coming soon which Shilun Fan (maybe cooperating
> > with Ahmar Suhail?)
> > has been actively working on getting the 3.4.0 release out.
> >
> > Considering the less updates for some active branches, should we
declare to
> > our downstream
> > users that some of these lines will EOL?
> >
> > IMO we should announce EOL branch-2.10 and branch-3.2 which are not
active
> > now.
> > Then we could focus on minor active branches (branch-3.3 and branch-3.4)
> > and increase release pace.
> >
> > So how about to keep branch-3.3 and branch-3.4 release lines as actively
> > maintained, And mark branch-2.10 and branch-3.2 EOL? Any opinions?
Thanks.
> >
> > Best Regards,
> > - He Xiaoqiao
> >
> > [1] https://hadoop.apache.org/releases.html
> > [2]
> >
> >
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Active+Release+Lines
> >

-
To unsubscribe, e-mail: private-unsubscr...@hadoop.apache.org
For additional commands, e-mail: private-h...@hadoop.apache.org

Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64

2023-12-05 Thread Apache Jenkins Server 
For more details, see 
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/

No changes




-1 overall


The following subsystems voted -1:
compile golang hadolint mvninstall mvnsite pathlen unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck whitespace


   mvninstall:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-mvninstall-root.txt
  [56K]

   compile:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-compile-root.txt
  [32K]

   cc:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-compile-root.txt
  [32K]

   golang:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-compile-root.txt
  [32K]

   javac:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-compile-root.txt
  [32K]

   checkstyle:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/buildtool-patch-checkstyle-root.txt
  [20K]

   hadolint:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/diff-patch-hadolint.txt
  [4.0K]

   mvnsite:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-mvnsite-root.txt
  [20K]

   pathlen:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/pathlen.txt
  [12K]

   pylint:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/diff-patch-pylint.txt
  [20K]

   shellcheck:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/diff-patch-shellcheck.txt
  [72K]

   whitespace:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/whitespace-eol.txt
  [12M]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/whitespace-tabs.txt
  [1.3M]

   javadoc:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-javadoc-root.txt
  [36K]

   unit:

   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-assemblies.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-build-tools.txt
  [20K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-annotations.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-auth.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-auth-examples.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-kms.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-minikdc.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-common-project_hadoop-nfs.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-client.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-httpfs.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
  [4.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-nfs.txt
  [8.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
  [8.0K]
   
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1232/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs_src_contrib_bkjournal.txt
  [4.0K]

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64

2023-12-05 Thread Apache Jenkins Server 
For more details, see 
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/

[Dec 4, 2023, 1:16:38 PM] (github) HDFS-17218. NameNode should process time out 
excess redundancy blocks (#6176). Contributed by Haiyang Hu.
[Dec 4, 2023, 1:19:33 PM] (github) HDFS-17250. 
EditLogTailer#triggerActiveLogRoll should handle thread Interrupted (#6266). 
Contributed by Haiyang Hu.




-1 overall


The following subsystems voted -1:
blanks hadolint pathlen xml


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

XML :

   Parsing Error(s): 
   
hadoop-common-project/hadoop-common/src/test/resources/xml/external-dtd.xml 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-excerpt.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags2.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-sample-output.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/fair-scheduler-invalid.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/yarn-site-with-invalid-allocation-file-ref.xml
 
  

   cc:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-compile-cc-root.txt
 [96K]

   javac:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-compile-javac-root.txt
 [12K]

   blanks:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/blanks-eol.txt
 [15M]
  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/blanks-tabs.txt
 [2.0M]

   checkstyle:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-checkstyle-root.txt
 [13M]

   hadolint:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-hadolint.txt
 [24K]

   pathlen:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-pathlen.txt
 [16K]

   pylint:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-pylint.txt
 [20K]

   shellcheck:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-shellcheck.txt
 [24K]

   xml:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/xml.txt
 [24K]

   javadoc:

  
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1431/artifact/out/results-javadoc-javadoc-root.txt
 [244K]

Powered by Apache Yetus 0.14.0-SNAPSHOT   https://yetus.apache.org

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-19004) S3A: Move to a new HttpSigner for S3Express

2023-12-05 Thread Steve Loughran (Jira) 
Steve Loughran created HADOOP-19004:
---

 Summary: S3A: Move to a new HttpSigner for S3Express
 Key: HADOOP-19004
 URL: https://issues.apache.org/jira/browse/HADOOP-19004
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs/s3
Affects Versions: 3.4.0
Reporter: Steve Loughran
Assignee: Harshit Gupta


The latest AWS SDK changes how signing works, and for signing S3Express 
signatures the new {{software.amazon.awssdk.http.auth}} auth mechanism is needed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Resolved] (HADOOP-18961) S3A: add s3guard command "bucket" to create buckets

2023-12-05 Thread Steve Loughran (Jira) 


 [ 
https://issues.apache.org/jira/browse/HADOOP-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran resolved HADOOP-18961.
-
Fix Version/s: 3.4.0
   Resolution: Fixed

Fixed in HADOOP-18996

> S3A: add s3guard command "bucket" to create buckets
> ---
>
> Key: HADOOP-18961
> URL: https://issues.apache.org/jira/browse/HADOOP-18961
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3
>Affects Versions: 3.4.0
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>Priority: Major
> Fix For: 3.4.0
>
>
> cloudstore has an mkbucket command
> https://github.com/steveloughran/cloudstore/blob/main/src/main/site/mkbucket.md
> however, its v1 api, has problems with spans and needs rework for v2. Oh, and 
> it has not tests.
> * move the command into hadoop-aws
> * add a test or two, 
> * add a mapper of  409 to bad request, as "BucketAlreadyOwnedByYouException" 
> comes in as a 409.
> Testing will be tricky...as well as not actually wanting to create new 
> buckets, my test a/c doesn't even have the permission to do so.
> Proposed tests
> # invalid args must be rejected
> # trying to create the current bucket must be rejected. This happens even if 
> you lack the permission to create
> *No actual attempts to create a new bucket*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Resolved] (HADOOP-18955) AWS SDK v2: add path capability probe "fs.s3a.capability.aws.v2"

2023-12-05 Thread Steve Loughran (Jira) 


 [ 
https://issues.apache.org/jira/browse/HADOOP-18955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran resolved HADOOP-18955.
-
Fix Version/s: 3.4.0
   Resolution: Fixed

Fixed in HADOOP-18996

> AWS SDK v2: add path capability probe "fs.s3a.capability.aws.v2"
> 
>
> Key: HADOOP-18955
> URL: https://issues.apache.org/jira/browse/HADOOP-18955
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3
>Affects Versions: 3.4.0
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>Priority: Minor
> Fix For: 3.4.0
>
>
> Add a "hasPathCapability()" probe for s3a v2 builds to aid diagnostics 
> -avoids needing to look for specific s3a files on classpath. 
> plus bucket-info to enum all capabilities which may be present



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] Make some release lines EOL

2023-12-05 Thread Masatake Iwasaki 
+1 on marking 3.2 EOL.

For branch-2.10, just keeping cherry-picking critical our CVEs without
release sounds good.
If someone really want, I can try to put 2.10.3 up.
dev-support/bin/create-release looks still working with some trivial fixes.

On Tue, Dec 5, 2023 at 7:45 PM Steve Loughran
 wrote:
>
> +1 for making 3.3 and 3.4 the maintained lines
>
> 3.2.x we should say -as it is true- that the age of the dependencies is
> such that it is transitively insecure. To fix those, people must upgrade.
>
> For 2.10.x, we should think about whether to cherrypick our own CVEs there,
> but not actually do any new ASF releases.
> I couldn't even get hold of a java7 JDK to do the release even if I wanted
> to -the same must hold for many others; getting a new release qualified
> would be hard. Best to say "upgrade time'.
>
>
> This goes well with a 3.4.0 release, as there's a clear story: we have a
> new 3.4.x line stabilising, if you want something already stable move onto
> 3.3.x if you hadn't already
>
>
>
>
>
> On Mon, 4 Dec 2023 at 12:39, Xiaoqiao He  wrote:
>
> > Hi folks,
> >
> > There are many discussions about which release lines should we still
> > consider actively
> > maintained in history. I want to launch this topic again, and try to get a
> > consensus.
> >
> > From download page[1] and active branches page[2], we have the following
> > release lines:
> > Hadoop 3.3 Release (release-3.3.5 at Jun 22 2022),  360 commits checked in
> > since last release.
> > Hadoop 3.2 Release (release-3.2.4 at Jul 11, 2022) 36 commits checked in
> > since last release.
> > Hadoop 2.10 Release (release-2.10.2 at May 17, 2022) 24 commits checked in
> > since last release.
> >
> > And Hadoop 3.4.0 will be coming soon which Shilun Fan (maybe cooperating
> > with Ahmar Suhail?)
> > has been actively working on getting the 3.4.0 release out.
> >
> > Considering the less updates for some active branches, should we declare to
> > our downstream
> > users that some of these lines will EOL?
> >
> > IMO we should announce EOL branch-2.10 and branch-3.2 which are not active
> > now.
> > Then we could focus on minor active branches (branch-3.3 and branch-3.4)
> > and increase release pace.
> >
> > So how about to keep branch-3.3 and branch-3.4 release lines as actively
> > maintained, And mark branch-2.10 and branch-3.2 EOL? Any opinions? Thanks.
> >
> > Best Regards,
> > - He Xiaoqiao
> >
> > [1] https://hadoop.apache.org/releases.html
> > [2]
> >
> > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Active+Release+Lines
> >

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-19003) S3A Assume role tests failing against S3Express stores

2023-12-05 Thread Steve Loughran (Jira) 
Steve Loughran created HADOOP-19003:
---

 Summary: S3A Assume role tests failing against S3Express stores
 Key: HADOOP-19003
 URL: https://issues.apache.org/jira/browse/HADOOP-19003
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs/s3, test
Affects Versions: 3.4.0
Reporter: Steve Loughran


The test suits which assume roles with restricted permissions down paths still 
fail on S3Express, even after disabling createSession.

This is with a role which *should* work.

Either the role setup is wrong, or there's something special about role 
configuration for S3Express buckets



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-19002) Delete invalid code logic

2023-12-05 Thread zhangzhanchang (Jira) 
zhangzhanchang created HADOOP-19002:
---

 Summary: Delete invalid code logic
 Key: HADOOP-19002
 URL: https://issues.apache.org/jira/browse/HADOOP-19002
 Project: Hadoop Common
  Issue Type: Bug
Reporter: zhangzhanchang






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] Make some release lines EOL

2023-12-05 Thread Steve Loughran 
+1 for making 3.3 and 3.4 the maintained lines

3.2.x we should say -as it is true- that the age of the dependencies is
such that it is transitively insecure. To fix those, people must upgrade.

For 2.10.x, we should think about whether to cherrypick our own CVEs there,
but not actually do any new ASF releases.
I couldn't even get hold of a java7 JDK to do the release even if I wanted
to -the same must hold for many others; getting a new release qualified
would be hard. Best to say "upgrade time'.


This goes well with a 3.4.0 release, as there's a clear story: we have a
new 3.4.x line stabilising, if you want something already stable move onto
3.3.x if you hadn't already





On Mon, 4 Dec 2023 at 12:39, Xiaoqiao He  wrote:

> Hi folks,
>
> There are many discussions about which release lines should we still
> consider actively
> maintained in history. I want to launch this topic again, and try to get a
> consensus.
>
> From download page[1] and active branches page[2], we have the following
> release lines:
> Hadoop 3.3 Release (release-3.3.5 at Jun 22 2022),  360 commits checked in
> since last release.
> Hadoop 3.2 Release (release-3.2.4 at Jul 11, 2022) 36 commits checked in
> since last release.
> Hadoop 2.10 Release (release-2.10.2 at May 17, 2022) 24 commits checked in
> since last release.
>
> And Hadoop 3.4.0 will be coming soon which Shilun Fan (maybe cooperating
> with Ahmar Suhail?)
> has been actively working on getting the 3.4.0 release out.
>
> Considering the less updates for some active branches, should we declare to
> our downstream
> users that some of these lines will EOL?
>
> IMO we should announce EOL branch-2.10 and branch-3.2 which are not active
> now.
> Then we could focus on minor active branches (branch-3.3 and branch-3.4)
> and increase release pace.
>
> So how about to keep branch-3.3 and branch-3.4 release lines as actively
> maintained, And mark branch-2.10 and branch-3.2 EOL? Any opinions? Thanks.
>
> Best Regards,
> - He Xiaoqiao
>
> [1] https://hadoop.apache.org/releases.html
> [2]
>
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Active+Release+Lines
>