I think it comes down to "do you think somebody else needs to review it?".
I do like to test before a cherrypick -at least of all the tests which
the patch changed, and for object store stuff a full test run is good due
diligence, but I think at least for me
cherrypick no merge issues: local comp
Extend for a bit from the last RC, as it takes time to qualify.
I'm busy testing, doing
- packaging &c
- CLI working with abfs and s3, both fs and cloudstore library calls
- building downstream projects (so validating maven artifacts). cloudstore
and spark there
- building downstream of downstrea
On Thu, 3 Jun 2021 at 07:14, Akira Ajisaka wrote:
> Dear Hadoop developers,
>
> Given the feedback from the discussion thread [1], I'd like to start
> an official vote
> thread for the community to vote and start the 3.1 EOL process.
>
> What this entails:
>
> (1) an official announcement that no
+1, binding.
Awesome piece of work!
I've done three forms of qualification, all related to s3 and azure storage
1. tarball validate, CLI use
2. build/test of downstream modules off maven artifacts; mine and some
other ASF ones. I (and it its very much me) have broken some downstream
+1
if you look closely the hadoop-azure module went to 100 lines a while back
and all is good
On Wed, 19 May 2021 at 22:13, Sean Busbey wrote:
> Hello!
>
> What do folks think about changing our line length guidelines to allow for
> 100 character width?
>
> Currently, we tell folks to follow th
not sure about stale PR closing; when you've a patch which is still pending
review it's not that fun to have it closed.
maybe better to have review sessions. I recall many, many years ago
attempts to try and catch up with all outstanding patch reviews.
On Wed, 14 Jul 2021 at 03:00, Akira Ajisa
I'm testing how well a backport of the latest AWS SDK goes; if all is
docile there then I'll merge that. Due diligence more than anything
elseone of the shaded netty JARs (never used by our code) has a CVE in
older versions
On Mon, 2 Aug 2021 at 08:07, Akira Ajisaka wrote:
> Hi Steven,
>
> M
Base.setup(AbstractFSContractTestBase.java:193)
On Tue, 3 Aug 2021 at 19:41, Brahma Reddy Battula wrote:
> Hi Steve,
>
> Is there any jira for this ??
>
>
>
> On Tue, 3 Aug 2021 at 4:05 PM, Steve Loughran >
> wrote:
>
> > I'm testing how well a backpo
On Tue, 2 Nov 2021 at 21:16, Sergey Shabalov <
sergey.shaba...@metaintegration.com> wrote:
> I try to use a simple code
>
>
>1. conf.set("fs.defaultFS","wasbs://
> sshcon...@sshblobhierarchyoff.blob.core.windows.net");
>2. conf.set("fs.azure.ssl.channel.mode","Default_JSS
I'll do my best to test this; I'm a bit broken right now.
I think we should mention in a release notes that is the version of a log4j
included in this and all previous releases is not vulnerable. But provide a
list plus links to any that have been fixed
On Fri, 10 Dec 2021 at 02:09, Chao Sun wro
On Tue, 14 Dec 2021 at 22:56, Chao Sun wrote:
> Thanks all for taking a look! looks like we need another RC addressing the
> following issues.
>
> > 1. the overview page of the doc is for the Hadoop 3.0 release. It would
> be best to base the doc on top of Hadoop 3.3.0 overview page. (it's a miss
okhttp was last updated in 2017
why use this over httpclient? its only used in a couple of places and
removing it entirely would make this problem go away forever
-- Forwarded message -
From: Eugene Shinn (Truveta) (Jira)
Date: Wed, 5 Jan 2022 at 19:48
Subject: [jira] [Created] (
DirectBufferPool does the weak refs effectively, but it only recycles
buffers of the same size; the elastic one will return the first largest
buffer.
I think we may want to have a variant of the ElasticBufferPool which uses
weak refs..we can adopt that and leave the (old) one alone. It is marked a
thanks, i'm on it..will run the aws and azure tests and then play with the
artifacts
On Wed, 19 Jan 2022 at 17:50, Chao Sun wrote:
> Hi all,
>
> I've put together Hadoop 3.3.2 RC2 below:
>
> The RC is available at:
> http://people.apache.org/~sunchao/hadoop-3.3.2-RC2/
> The RC tag is at:
> https
On Thu, 20 Jan 2022 at 17:15, Andrew Purtell
wrote:
> Just to clarify: I think you want to upgrade to Log4J2 (or switch to
> LogBack) as a strategy for new releases, but you have the option in
> maintenance releases to use Reload4J to maintain Appender API and
> operational compatibility, and use
*+1 binding.*
reviewed binaries, source, artifacts in the staging maven repository in
downstream builds. all good.
*## test run*
checked out the asf github repo at commit 6da346a358c into a location
already set up with aws and azure test credentials
ran the hadoop-aws tests with -Dparallel-test
`now some bad news
https://issues.apache.org/jira/browse/HADOOP-18091
S3A auditing leaks memory through ThreadLocal references
surfaces in processes with long lived threads creating and destroying many
s3a FS instances.
working on a fix right now
On Fri, 21 Jan 2022 at 21:02, Eric Payne
wrote:
fix is in t disable auditing, which is now the default
https://issues.apache.org/jira/browse/HADOOP-18094
everything is OK for apps which retain the same fs instances for the life
of the app, but not for Hive...
will do a better fix ASAP where in exchange for loss of auditing after a GC
event, on
that error
org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-default-http-blocker (
http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet
implies maven is not downloading http artifacts, and it had decided that
the reslet artifacts were coming off an http repo, even though its in mav
maybe even before moving the catalog away, we could make it optional
On Fri, 28 Jan 2022 at 08:24, Akira Ajisaka wrote:
> Thank you Masatake and Chao!
>
> On Fri, Jan 28, 2022 at 5:11 PM Chao Sun wrote:
>
> > Thanks Masatake and Akira for discovering the issue. I used
> > `dev-support/bin/creat
I've just created a new JIRA and assigned to myself: HADOOP-18198. Release
Hadoop 3.3.3: hadoop-3.3.2 with CVE fixes
https://issues.apache.org/jira/browse/HADOOP-18198
--
Hadoop 3.3.3 is a minor followup release to Hadoop 3.3.2 with
* CVE fixes in Hadoop source
* CVE fixes in d
vulnerabilities which were never reached in the Hadoop code, but which
audit tools would flag up.
I'd also like to update our shaded protobuf library too
On Mon, 11 Apr 2022 at 14:54, Steve Loughran wrote:
>
> I've just created a new JIRA and assigned to myself: HADOOP-18198.
There is now a branch-3.3.3 in the repo; this is forked off 3.3.2, *not*
branch-3.3
branch-3.3 has its hadoop version now set to 3.3.4
I've renamed the release version 3.3.3 in JIRA to 3.3.4, so all
fixed/target/affects references have been automatically updated. text
references in JIRAs and PRs
I have put together a release candidate (rc0) for Hadoop 3.3.3
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC0/
The git tag is release-3.3.3-RC0, commit d37586cbda3
The maven artifacts are staged at
https://repository.apache.org/content/repositories/orgapachehadoo
I'm not enthusiastic here as it not only makes the builds slower, it
reduces the #of builds we can through a day
one thing I am wondering is could we remove java8 support on some branches?
make branch 3.3.2.x (i.e the 3.3.3 release) the last java 8 build, and this
summers branch-3.3 release (whic
gt; - mvn clean install -DskipTests
> > >>>> - mvn -fae --no-transfer-progress -DskipTests
> > -Dmaven.javadoc.skip=true
> > >>>> -Pnative -Drequire.openssl -Drequire.snappy -Drequire.valgrind
> > >>>> -Drequire.zstd -Dreq
gt; >> to compensate for this time.
> >>
> >> For now lets just integrate it our nightly builds only and circle back
> >> again here in future if the need be.
> >>
> >> -Ayush
> >>
> >>> On Fri, 6 May 2022 at 20:44, Wei-Chiu C
)
> >>>>>>
> >>>>>> * Signature: ok
> >>>>>> * Checksum : passed
> >>>>>> * Rat check (1.8.0_191): passed
> >>>>>>- mvn clean apache-rat:check
> >>>>>> * Built from
staged-releases
>https://repository.apache.org/content/repositories/staging/
>
>
> true
>
>
> true
>
>
>
> to the `` section in your Maven pom.xml file.
>
> On Mon, May 9, 2022 at 8:52 AM Steve
version in staging with the files; still don't know how the
previous delete lacked them, I will do more testing tomorrow before putting
up the next RC. which will be off the same git commit as before, just a
rebuild, repackage and republish.
-Steve
On Tue, 10 May 2022 at 00:18, Steve Lou
I have put together a release candidate (RC1) for Hadoop 3.3.3
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC1/
The git tag is release-3.3.3-RC1, commit d37586cbda3
The maven artifacts are staged at
https://repository.apache.org/content/repositories/orgapachehadoo
c.
> > > >
> > > > Thanks Steve for your work.
> > > >
> > > > - He Xiaoqiao
> > > >
> > > > On Mon, May 16, 2022 at 4:25 AM Viraj Jasani
> > wrote:
> > > > >
> > > > > +1 (non-bind
On behalf of the Apache Hadoop Project Management Committee, I'm pleased to
announce that Hadoop 3.3.3 has been
released:
https://hadoop.apache.org/release/3.3.3.html
This is the third stable release of the Apache Hadoop 3.3 line.
It contains 23 bug fixes, improvements and enhancements since 3.3
+1 binding
I've extended my validator project
https://github.com/steveloughran/validate-hadoop-client-artifacts
it now
* fetches KEYS
* fetches an RC from a remote url
* validates signing
* untars and tries to build source
* untars binary release and tries some native commands
the source build f
I want to start a quick discussion on a plan for hadoop releases this
summer. I am willing to do the release manager work. Mukund and Mehakmeet
have have already volunteered to help even if they don't know that yet.
I've got two goals
1. minor followup to 3.3.3
2. feature release of new stu
I've just created an initial project "fs-api-shim" to provide controlled
access to the hadoop 3.3.3+ filesystem API calls on hadoop 3.2.0+ releases
https://github.com/steveloughran/fs-api-shim
The goal here is to make it possible for core file format libraries
(Parquet, Avro, ORC, Arrow etc) and o
I'm setting things up for a new release
https://issues.apache.org/jira/browse/HADOOP-18305
absolute minimum of fixes. as well as some related to ZK lockdown, i would
like to include
https://issues.apache.org/jira/browse/HADOOP-18303
remove shading exclusion of javax.ws.rs-api from hadoop-client-
n, 20 Jun 2022 at 19:02, Steve Loughran wrote:
> I'm setting things up for a new release
>
> https://issues.apache.org/jira/browse/HADOOP-18305
>
> absolute minimum of fixes. as well as some related to ZK lockdown, i would
> like to include
>
> https://issues.apa
I have put together a release candidate (RC0) for Hadoop 3.3.4
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC0/
The git tag is release-3.3.4-RC0, commit c679bc76d26
The maven artifacts are staged at
https://repository.apache.org/content/repositories/orgapac
u, 21 Jul 2022 at 19:07, Steve Loughran wrote:
>
> I have put together a release candidate (RC0) for Hadoop 3.3.4
>
> The RC is available at:
> https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC0/
>
> The git tag is release-3.3.4-RC0, commit c679bc76d26
>
> T
Is there any WiP which people consider a blocker for a 3.3.x feature
release to follow the 3.3.4 security/critical integration issues release?
I want to split off the fork for that next release off branch-3.3 and start
stabilising.
are there things people working on which are nearly ready?
I have put together a release candidate (RC1) for Hadoop 3.3.4
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC1/
The git tag is release-3.3.4-RC1, commit a585a73c3e0
The maven artifacts are staged at
https://repository.apache.org/content/repositories/orgapac
local projects
https://github.com/steveloughran/validate-hadoop-client-artifacts
all good as far as my test coverage goes, with these projects validating
the staged dependencies.
now, who else can review
On Fri, 29 Jul 2022 at 19:47, Steve Loughran wrote:
>
>
> I have put together
The vote passed with the following result.
Binding PMC members:
+1 Chris Nauroth
+1 Steve Loughran
+1 Masatake Iwasaki
Non binding votes:
+1 Ashutosh Gupta
Cheng Pan was worried about the new transient kotlin dependency. They are
working on a PR there which we can target for the successor to
top
> of it and all passed. Did some kills, stuff came back.
>
> I didn't spend time on unit tests but one set passed on a local rig here:
>
> [image: image.png]
> Stack
>
> On Fri, Jul 29, 2022 at 11:48 AM Steve Loughran
> wrote:
>
>> I have put together
On behalf of the Apache Hadoop Project Management Committee, I am
pleased to announce the release of Apache Hadoop 3.3.4.
---
This is a release of Apache Hadoop 3.3 line.
It contains a small number of security and critical integration fixes since
3.3.3.
Users of Apache Hadoop 3.3.3 should upgrad
I'm afraid not. protobuf maybe compatible at the wire level -the marshalled
data is good-, but the generated classes in jars Will not link to any
version other than that they were explicitly compiled with.
this is why hadoop 3.3 has a private shaded copy in the hadoop-thirdparty
JAR -how to stop th
Hi
Mukund Thakur plans to fork off the next branch-3.3. release in 10 days
time. last chance to get changes in.
I'm away next week...try not to break the branch. Any testing you can do
would be appreciated
Steve
Mukund has just created the new Hadoop release JIRA,
https://issues.apache.org/jira/browse/HADOOP-18470, and is doing the first
build/test before pushing it up. This is off branch-3.3, so it will have
more significant changes than the 3.3.3 and 3.3.4 releases, which were just
CVE/integration fixes.
tests needed tuning
fixed now HADOOP-18401
>
>
> On Tue, Sep 27, 2022 at 9:35 AM Steve Loughran >
> wrote:
>
> > Mukund has just created the new Hadoop release JIRA,
> > https://issues.apache.org/jira/browse/HADOOP-18470, and is doing the
> first
> > build
The first "smoke test" RC is about to be up for people to play with, we are
just testing things here and getting that arm build done.
Can I have some content for the index.html page describing what has changed?
hadoop-project/src/site/markdown/index.md.vm
I can (and will) speak highly of stuff I'
Mukund and I have put together a release candidate (RC0) for Hadoop 3.3.5.
Given the time of year it's a bit unrealistic to run a 5 day vote and
expect people to be able to test it thoroughly enough to make this the one
we can ship.
What we would like is for anyone who can to verify the tarballs,
thanks
pulling in a few of the recent changes which seem needed/important, now
wondering about the javadocs.
i will add a new probe for this in our automated release ant bulld so we
can't cut a release without that
https://github.com/steveloughran/validate-hadoop-client-artifacts
On Mon, 2 Jan 2
Apache Hadoop 3.3.5
Mukund and I have put together a release candidate (RC1) for Hadoop 3.3.5.
What we would like is for anyone who can to verify the tarballs, especially
anyone who can try the arm64 binaries as we want to include them too.
The RC is available at:
https://dist.apache.org/repos/d
03
> > - HDFS-16310
> > - HADOOP-18014
> >
> > I corrected all the wrong fix versions just now. I'm not sure we should
> > revote it since it only affects the changelog.
> >
> > - Takanobu
> >
> > 2023年2月21日(火) 22:43 Steve Loughran :
> >
>
over time. Going to
revert HADOOP-18590. Publish SBOM artifacts (#5281)
On Thu, 23 Feb 2023 at 10:29, Steve Loughran wrote:
> ok, let me cancel, update those jiras and kick off again. that will save
> anyone else having to do their homework
>
> On Thu, 23 Feb 2023 at 08:56, Tak
without that file being up to
date, but at least all the transitive stuff is correctly licensed. And i
think we need to change the PR template to mention transitive updates in
the license bit too
if this goes in, I will do the rebuild on monday UK time
On Thu, 23 Feb 2023 at 11:18, Steve Loughran
Mukund and I have put together a release candidate (RC2) for Hadoop 3.3.5.
We need anyone who can to verify the source and binary artifacts,
including those JARs staged on maven, the site documentation and the arm64
tar file.
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/h
like to see about merging to branch-3.3.5 as well.
>
> Thanks for the consideration and sorry for not bringing this up in RC1 or
> earlier.
>
> On Mon, Feb 27, 2023 at 9:59 AM Steve Loughran >
> wrote:
>
> > Mukund and I have put together a release candidate (RC2)
> * Ran Hbase (latest 2.5) tests against Hdfs, ran RowCounter Mapreduce job
>> * Hdfs CRUD tests
>> * MapReduce wordcount job
>>
>> * Ran S3A tests with scale profile against us-west-2:
>> mvn clean verify -Dparallel-tests -DtestsThreadCount=8 -Dscale
>>
>> I
>> - mvn clean install -DskipTests
>> >> * Built tar from source (1.8.0_341): ok
>> >> - mvn clean package -Pdist -DskipTests -Dtar
>> -Dmaven.javadoc.skip=true
>> >>
>> >> * Built images using the tarball, installed and started all o
imeout).
>
>
> On Sat, Mar 4, 2023 at 4:29 AM Steve Loughran >
> wrote:
>
> > On Sat, 4 Mar 2023 at 01:47, Erik Krogen wrote:
> >
> > > Thanks Steve. I see now that the branch cut was way back in October so
> I
> > > definitely understand your
does not exist (#5400) [ZanderXu <
> zande...@apache.org
> >]
> * 44bf8aadedf 2023-03-03 HDFS-16832. [SBN READ] Follow-on to HDFS-16732.
> Fix NPE when check the block location of empty directory (#5099)
> [zhengchenyu ]
> * 72f8c2a4888 (tag: release-3.3.5-RC2) 2023-02-25 HADOOP-18641
Apache Hadoop 3.3.5
Mukund and I have put together a release candidate (RC3) for Hadoop 3.3.5.
What we would like is for anyone who can to verify the tarballs, especially
anyone who can try the arm64 binaries as we want to include them too.
The RC is available at:
https://dist.apache.org/repos/d
1. I think a new interface would be good as FileContext could do the
same thing
2. using PathCapabilities probes should still be mandatory as for
FileContext it would depend on the back end
3. Whoever does this gets to specify what the API does and write the
contract tests. Saying
ypto.so
ISA-L: false libhadoop was built without ISA-L support
PMDK:false The native code was built without PMDK support.
---
On Wed, 15 Mar 2023 at 19:47, Steve Loughran wrote:
>
> Apache Hadoop 3.3.5
>
> Mukund and I have put together a release candidate (RC3) for Hadoop 3.3.5.
>
with scale profile looks good
>
>
> On Wed, Mar 15, 2023 at 12:48 PM Steve Loughran
>
> wrote:
>
> > Apache Hadoop 3.3.5
> >
> > Mukund and I have put together a release candidate (RC3) for Hadoop
> 3.3.5.
> >
> > What we would like is for anyon
ok, here's my summary, even though most of the binding voters forgot to
declare they were on the PMC.
+1 binding
Steve Loughran
Chris Nauroth
Masatake Iwasaki
Ayush Saxena
Xiaoqiao He
+1 non-binding
Viraj Jasani
0 or -1 votes: none.
Accordingly: the release is good!
I will send the f
On behalf of the Apache Hadoop Project Management Committee, I am
pleased to announce the release of Apache Hadoop 3.3.5.
This is a release of Apache Hadoop 3.3 line.
Key changes include
* A big update of dependencies to try and keep those reports of
transitive CVEs under control -both genuin
On Thu, 23 Mar 2023 at 10:07, Ayush Saxena wrote:
>
> Second idea mentioned in the original mail is also similar to mentioned in
> the comment in the above ticket and is still quite acceptable, name can be
> negotiated though, Add an interface to pull the relevant methods up in that
> without tou
outgrown checked exceptions
On Fri, 24 Mar 2023 at 09:44, Steve Loughran wrote:
>
>
> On Thu, 23 Mar 2023 at 10:07, Ayush Saxena wrote:
>
>>
>> Second idea mentioned in the original mail is also similar to mentioned in
>> the comment in the above ticket and is still
Now that hadoop 3.3.5 is out, i want to propose something new
we switch branch-3.3 and trunk to being java11 only
1. java 11 has been out for years
2. oracle java 8 is no longer available under "premier support"; you
can't really get upgrades
https://www.oracle.com/java/technologies
ongoing major dependency upgrades (log4j 1 to 2, jersey 1
> to 2 and junit 4 to 5) are blockers for java 11 compile + test stability.
>
>
> On Tue, Mar 28, 2023 at 4:55 AM Steve Loughran >
> wrote:
>
> > Now that hadoop 3.3.5 is out, i want to propose something new
>
for your studious pursuit of this goal.
>
> Thanks,
> Nick
>
> On Mon, Mar 27, 2023 at 4:58 AM Steve Loughran >
> > wrote:
> >
> > > side issue, as i think about what bulk delete call would also keep
> hbase
> > > happy
> > >
disable it. Will do it
> tomorrow, if nobody objects. In case the one who configured it wants
> to do it early, feel free to do so.
>
> We already have one for branch-3.3 which runs weekly which most
> probably most of us don't follow :)
>
> -Ayush
>
> On Wed, 22 Mar 2
Wei-Chiu has suggested a minimal "things in 3.3.5 which were very broken,
api change for ozone and any critical jar updates"
so much lower risk/easier to qualify and ship.
I need to get https://issues.apache.org/jira/browse/HADOOP-18724 in here;
maybe look at a refresh of the "classic" jars (slf4
Which branch is -3.3.6 off? 3.3.5 or 3.3?
I'm travelling for the next few days and unlikely to be able to test this;
will do my best
On Wed, 14 Jun 2023 at 07:27, Wei-Chiu Chuang wrote:
> I am inviting anyone to try and vote on this release candidate.
>
> Note:
> This is built off branch-3.3.6
1. we should patch gcs, to ignore those new keys.
2. i may be able to validate RC1 this weekend
On Fri, 16 Jun 2023 at 03:20, Wei-Chiu Chuang
wrote:
> Overall so far so good.
>
> hadoop-api-shim:
> built, tested successfully.
>
> cloudstore:
> built successfully.
>
> Spark:
> built successfull
could be good.
why not set it up for the third-party module first to see how well it works?
On Tue, 18 Jul 2023 at 21:05, Ayush Saxena wrote:
> Something we can explore as well!!
>
> -Ayush
>
> Begin forwarded message:
>
> > From: Volkan Yazıcı
> > Date: 19 July 2023 at 1:24:49 AM IST
> > To:
We don't have a complete set of shaded artefacts -so it's not fair to point
at the downstream users and say it's "your own fault". We need to do more
here ourselves.
Here: it is a CVE, they should upgrade anyway. Guava is special because it
has been so brittle cross versions and so widely used by
On Thu, Nov 21, 2019 at 11:49 PM Jonathan Hung wrote:
> Thanks for the detailed thoughts, everyone.
>
> Eric (Badger), my understanding is the same as yours re. minor vs patch
> releases. As for putting features into minor/patch releases, if we keep the
> convention of putting new features only i
I just submitted a pull request for HDFS.
https://github.com/apache/hadoop/pull/1747
yetus failed -docker problems. is this common?
en.
> I too observed it for a PR this morning, This wasn’t there couple of days
> back.
> May be we need to inform the Infra people.
>
> https://github.com/apache/hadoop/pull/1748#issuecomment-563894996
>
> -Ayush
> > On 10-Dec-2019, at 4:17 PM, Steve Loughran
> wrote:
&g
its this https://issues.apache.org/jira/browse/HADOOP-16754
On Tue, Dec 10, 2019 at 1:41 PM Steve Loughran wrote:
> not infra, docker, ubuntu can't find a repo jonathonf/ghc-8.0.2 . One
> which got deleted yesterday
>
> https://launchpad.net/~jonathonf
>
> This is in hado
I'm thinking of doing a backport of most of the hadoop-aws changes to
branch-3.2, for the next 3.2.x release; they are all self contained and
will benefit many (they will need to cope with the older mockito version,
but I have to deal with that in-house already).
one change is the new openFile() b
>
> 2. Features close to finish:
>
>
> *HADOOP-15620: Über-jira: S3A phase VI: Hadoop 3.3 features. ( owner
> : Steve Loughran)
> *HADOOP-15763: Über-JIRA: abfs phase II: Hadoop 3.3 features &
> fixes. ( owner : Steve Loughran)
> *HADOOP-15
Well volunteered! I will help with the testing
On Mon, Jan 6, 2020 at 10:08 AM Gabor Bota
wrote:
> I'm interested in doing a release of hadoop.
> The version we need an RM is 3.1.3 right? What's the target date for that?
>
> Thanks,
> Gabor
>
> On Mon, Jan 6, 2020 at 8:31 AM Akira Ajisaka wrote
https://issues.apache.org/jira/browse/HDFS-13616
I don't want to be territorial here -but as I keep reminding this list
whenever it happens, -I do not want any changes to go into the core
FileSystem class without
* raising a HADOOP- JIRA
* involving those of us who work on object stores. We have
especially since Gabor and I have just
been dealing with S3 delete throttling issues.
I will gladly give advice there. at the very least, it must implement
Progressable, so when deletes are very slow processes/threads can still
send heartbeats back. It also sets expectations up as to how long some
FYI, looks like the ASF git repo @
https://gitbox.apache.org/repos/asf/hadoop.git and the github repo at
https://github.com/apache/hadoop.git have lost sync;
I've merged a couple of changes in via the github UI and they aren't
surfacing in the asf repo, which is still @ commit 60fa15366e8, YARN-1
Okay.
I am not going to be a purist and say "what were they doing -using our
private APIs?" because as we all know, with things like UGI tagged @private
there's been no way to get something is done without getting into the
private stuff.
But why did we do the protobuf changes? So that we could up
+1, with the instruction "warn everyone about the guava update possibly
breaking things at run time"
With the key issues being
* code compiled with the new guava release will not link against the older
releases, even without any changes in the source files.
* this includes hadoop-common
Applicati
hmm
YARN-9341 went through all of the yarn lock code -it's in 3.3 but not in
3.1. And we do not want to attempt to backport 175KB of lock
acquire/release code, do we?
anyone in yarn-dev got any thoughts here?
On Sun, 5 Jul 2020 at 22:14, Masatake Iwasaki
wrote:
> Thanks for putting this up, Ga
There's a broader issue here which is "S3A support for buckets with Object
Lock"
I suspect that there will be more to this than just setting an MD5 checksum
on file uploads.
AFAIK, nobody has done this/is working on the feature; there's so many
other issues than nobody is going to do it unless it
+1
did a cloudstore clean build and test
did as well as I could with a spark build.
For anyone having maven problems building hadoop on a mac, homebrew now
forces its version of maven to use a homebrew specific openjdk 11
(one /usr/libexec/java_home doesn't locate); bits of the hadoop build don'
I should add, that's a binding +1
On Mon, 27 Jul 2020 at 19:55, Steve Loughran wrote:
> +1
>
> did a cloudstore clean build and test
> did as well as I could with a spark build.
>
> For anyone having maven problems building hadoop on a mac, homebrew now
> forces its
+1
are there any Hadoop branch-2 releases planned, ever? If so I'll need to
backport my s3a directory compatibility patch to whatever is still live.
On Thu, 27 Aug 2020 at 06:55, Wei-Chiu Chuang wrote:
> Bump up this thread after 6 months.
>
> Is anyone still interested in the 2.9 release line
+1
binding
On Mon, 31 Aug 2020 at 20:09, Wei-Chiu Chuang wrote:
> Dear fellow Hadoop developers,
>
> Given the overwhelming feedback from the discussion thread
> https://s.apache.org/hadoop2.9eold, I'd like to start an official vote
> thread for the community to vote and start the 2.9 EOL proce
+1, binding
On Fri, 25 Sep 2020 at 06:59, Elek, Marton wrote:
> Hi all,
>
> Thank you for all the feedback and requests,
>
> As we discussed in the previous thread(s) [1], Ozone is proposed to be a
> separated Apache Top Level Project (TLP)
>
> The proposal with all the details, motivation and h
Hi,
Can I get some reviews of this PR
https://github.com/apache/hadoop/pull/2323
It adds a new API, IOStatisticsSource, for any class to act as a source of
a static or dynamic IOStatistics set of counters/gauges/min/max/mean stats
The intent is to allow applications to collect statistics on stre
1 - 100 of 563 matches
Mail list logo
