Re: [DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

Thanks Owen, Yes I am aware of the optional category X. I was under the impression that the "optionality" need to be more explicit. For example, by adding true tag. https://medium.com/@danismaz.furkan/difference-between-optional-true-optional-and-scope-provided-scope-7404ec24fb59 In this case, RB

Re: [DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

The relevant url is https://www.apache.org/legal/resolved.html#optional On Fri, Jun 9, 2023 at 6:54 AM Owen O'Malley wrote: > We are allowed to use category X software in optional components. > Furthermore, the dependency is marked as provided, so it won't be pulled > into a transitive closure.

Re: [DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

We are allowed to use category X software in optional components. Furthermore, the dependency is marked as provided, so it won't be pulled into a transitive closure. You are right that I should have included a comment about that on the original jira. .. Owen On Fri, Jun 9, 2023 at 1:58 AM Wei-C

[DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

Hi community, While preparing for 3.3.6 RC, I realized the mysql-connector-java dependency added by HADOOP-18535 is GPL licensed. Source: https://github.com/mysql/mysql-connector-j/blob/release/8.0/LICENSE See legal discussion at Apache LEGAL-

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

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1052/ No changes ERROR: File 'out/email-report.txt' does not exist - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.o

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

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1251/ [Jun 7, 2023, 1:05:52 PM] (github) HADOOP-18740. S3A prefetch cache blocks should be accessed by RW locks (#5675) -1 overall The following subsystems voted -1: blanks hadolint pathlen unit

Re: [DISCUSS] Hadoop 3.3.6 release planning

Thanks for comments Looking at jiras fixed in 3.3.6 and 3.3.9 (my bad, forgot that most commits landing in branch-3.3 was 3.3.9), most are okay. We have about 119 commits so it's manageable. I am planning to cut 3.3.6 out of branch-3.3 later today. Anything open that is still targeting 3.3.6 will

[jira] [Resolved] (HDFS-17003) Erasure Coding: invalidate wrong block after reporting bad blocks from datanode

[ https://issues.apache.org/jira/browse/HDFS-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-17003. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > Erasure Coding: invalid

[jira] [Resolved] (HDFS-17035) FsVolumeImpl#getActualNonDfsUsed may return negative value

[ https://issues.apache.org/jira/browse/HDFS-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved HDFS-17035. - Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > FsVolumeImpl#getActua