+1
Thanks Owen.
—Matt
—
Open Source Technologies @
`This is not a contribution.`
On Jun 19, 2020, at 10:19 AM, Owen O'Malley wrote:
We unfortunately have a lot of master/slave and whitelist/blacklist
terminology usage in Hadoop. It will take a while to fix them all, but one
is easy to
Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and
hdfs-dev together or separate, I’m neutral.
Thanks,
—Matt
On Oct 23, 2019, at 2:11 PM, Elek, Marton wrote:
Thanks to report this problem Rohith,
Yes, it seems to be configured with the wrong mailing list.
I think the
Hi Candy,
It’s possible that you’ve already tried the below, but one can’t tell from your
message, so here goes:
1. Presumably you’ve read
https://hadoop.apache.org/docs/r3.2.0/hadoop-project-dist/hadoop-common/NativeLibraries.html
Admittedly it doesn’t answer your question, but it does point
Sorry I won’t be able to come today; a work meeting interferes.
—Matt
On Sep 4, 2019, at 9:10 AM, Wei-Chiu Chuang wrote:
It's a short week so I didn't set up a predefined topic to discuss.
What should we be discussing? How about Erasure Coding? I'm starting to see
tricky EC bug reports coming
+1 for publishing notes. Thanks!
On Aug 21, 2019, at 4:16 PM, Aaron Fabbri wrote:
Thank you Wei-Chiu for organizing this and sending out notes!
On Wed, Aug 21, 2019 at 1:10 PM Wei-Chiu Chuang mailto:weic...@apache.org>> wrote:
> We had a great turnout today, thanks to Konstantin for leading
Wangda and Eric,
We can express the intent, I think, by scheduling two recurring meetings:
- monthly, on the 2nd Wednesday, and
- monthly, on the 4th Wednesday.
This is pretty easy to understand, and not too onerous to maintain.
But I’m okay with simple bi-weekly too.
I’m neutral on 10 vs 11am,
Hi Wangda, thanks for this. A question about the schedule correction:
> > 1) In the proposal, repeats are not properly. (I used bi-weekly instead of
> 2nd/4th week as repeat frequency). I'd like to fix the frequency on Thu and
> it will take effect starting next week.
I understand that
[
https://issues.apache.org/jira/browse/HADOOP-16166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-16166.
-
Resolution: Fixed
> TestRawLocalFileSystemContract fails with build Docker container runn
Matt Foley created HADOOP-16166:
---
Summary: TestRawLocalFileSystemContract fails with build Docker
container running on Mac
Key: HADOOP-16166
URL: https://issues.apache.org/jira/browse/HADOOP-16166
[
https://issues.apache.org/jira/browse/HADOOP-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-7809.
Resolution: Won't Do
Aged out.
> Backport HADOOP-5839 to 0.20-security - fixes to ec2 scri
[
https://issues.apache.org/jira/browse/HADOOP-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-9359.
Resolution: Won't Fix
Closed due to evident insufficient interest.
> Add Windows build and u
Matt Foley created HADOOP-13382:
---
Summary: remove unneeded commons-httpclient dependencies from POM
files in Hadoop and sub-projects
Key: HADOOP-13382
URL: https://issues.apache.org/jira/browse/HADOOP-13382
[
https://issues.apache.org/jira/browse/HADOOP-12617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-12617.
-
Resolution: Fixed
Fix Version/s: 2.8.0
> SPNEGO authentication request to non-defa
Matt Foley created HADOOP-12617:
---
Summary: SPNEGO authentication request to non-default realm gets
default realm name inserted in target server principal
Key: HADOOP-12617
URL: https://issues.apache.org/jira/browse
Yes, in terms of forward compatibility, my company has been certifying the
current Hadoop-related stack on JDK7 (both Oracle and OpenJDK) for some
time. No problems there, in our experience.
For stopping supporting JDK6 in the near future, and enabling JDK7 feature
usage, +1.
--Matt
On Tue,
On Mon, Aug 5, 2013 at 9:43 AM, Chris K Wensel ch...@wensel.net wrote:
any particular reason the 1.1.2 releases were pulled from the mirrors (so
quickly)?
On Aug 4, 2013, at 2:08 PM, Matt Foley ma...@apache.org wrote:
I'm happy to announce that Hadoop version 1.2.1 has passed its release
'stable' link that itself is updated to the actual
stable release.
we do this now with all of the cascading artifacts. it prevents automated
things from breaking immediately.
http://files.cascading.org/sdk/2.1/latest.txt
ckw
On Aug 5, 2013, at 11:20 AM, Matt Foley ma...@apache.org wrote
I'm happy to announce that Hadoop version 1.2.1 has passed its release vote
and is now available. It has 18 bug fixes and patches over the previous
1.2.0 release; please see Hadoop 1.2.1 Release
Noteshttp://hadoop.apache.org/docs/r1.2.1/releasenotes.htmlfor
details. This release of Hadoop-1.2 is
which will include Windows native compatibility.
My apologies, this was incorrect. Windows has only been integrated to
trunk and branch-2.1.
Thanks,
--Matt
On Sun, Aug 4, 2013 at 2:08 PM, Matt Foley ma...@apache.org wrote:
I'm happy to announce that Hadoop version 1.2.1 has passed its
cluster.
On Wed, Jul 24, 2013 at 2:08 PM, Matt Foley ma...@apache.org wrote:
Colleagues,
This is a stabilization release of the Hadoop-1.2 codeline. It has 18
patches over the 1.2.0 release, which may be seen in the Release
Notes
http://people.apache.org/~mattf/hadoop-1.2.1-rc0/releasenotes
Colleagues,
This is a stabilization release of the Hadoop-1.2 codeline. It has 18
patches over the 1.2.0 release, which may be seen in the Release
Noteshttp://people.apache.org/~mattf/hadoop-1.2.1-rc0/releasenotes-1.2.1.html.
Please vote on two items:
a) accepting this as an Apache Hadoop
The proposed RC-0 for Hadoop 1.2.1 has been
taggedhttp://svn.apache.org/viewvc/hadoop/common/tags/release-1.2.1-rc0/,
and performs satisfactorily wrt Unit Tests. However, my build environment
has been bolluxed up by changes in hardware, and I am still having problems
building the native-build
[
https://issues.apache.org/jira/browse/HADOOP-9730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-9730.
Resolution: Fixed
Fix Version/s: 1.2.1
+1. Thanks, Giri, that fixed the problem
[
https://issues.apache.org/jira/browse/HADOOP-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-9504.
Resolution: Fixed
Target Version/s: 0.23.8, 2.1.0-beta, 1.2.1 (was: 2.1.0-beta, 0.23.8
Colleagues,
Next weekend, starting the evening of Friday 7 June, a week from tomorrow,
I plan to cut a hadoop-1.2.1-rc0 from the branch-1.2 branch.
This is intended to be a stabilization release of 1.2. I request that
major new back-ports, or any change with significant risk, be put in
branch-1
Hi Cos,
I would also request that you renumber the release candidate to just
three-numbers, hence 2.0.5-alpha.
Arun, are you willing to start the 2.1.x name-space for your next release,
so that 2.0.x-alpha can become an intermediate stabilization branch as Cos
and Konst want?
I just think that
The vote closed last night, with very positive results:
+1 binding: 14
+1 non-binding: 12
-1 or 0: none
I'll work with Chris to get the Bylaws doc changed, but the change is
effective as of 7:05pm PDT May 28, 2013.
Many thanks,
--Matt
On Wed, May 22, 2013 at 2:04 AM, Matt Foley ma
Forgot to say: Vote will close one week after it started, at 7:05pm PDT on
Tuesday 28 May.
Thanks,
--Matt
On Tue, May 21, 2013 at 7:03 PM, Matt Foley ma...@apache.org wrote:
This was previously discussed in the thread [PROPOSAL] change in bylaws
to remove Release Plan vote. 13 people
Matt.
--Konstantin
On Tue, May 21, 2013 at 7:01 PM, Matt Foley ma...@apache.org wrote:
Ok, if no one complains I will phrase the vote to include +1's explicitly
cast in the discussion thread.
--Matt
On Tue, May 21, 2013 at 6:58 PM, Mattmann, Chris A (398J)
chris.a.mattm...@jpl.nasa.gov
Hi Jagane,
My response to your concerns is that I hope the PMC will have enough wisdom
not to pass votes for a confusing number of releases -- if only to avoid
the kind of fragmentation you point out could happen.
To date, however, this does not seem to have been a major problem in our
community.
I've now started a separate discussion thread in common-dev@, titled
[PROPOSAL] change in bylaws to remove Release Plan vote. If it achieves
consensus, I'll put it to a vote to so change the bylaws.
Best,
--Matt
On Sat, May 18, 2013 at 4:22 PM, Chris Douglas cdoug...@apache.org wrote:
The
wrote:
+1 (non-binding)
On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
jiten...@hortonworks.comwrote:
+1
On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote:
+1 thanks Matt.
On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote
, Matt Foley ma...@apache.org wrote:
13/14 +1's. I think that constitutes consensus. Moving this to a VOTE
thread. Please repeat your +1s :-)
Cheers,
--Matt
On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar maha...@hortonworks.com
wrote:
+1.
thanks
mahadev
On Tue, May 21
This was previously discussed in the thread [PROPOSAL] change in bylaws to
remove Release Plan vote. 13 people explicitly cast +1s in that thread.
Absent objection I will count those as votes without requiring them to
(re-)respond to this VOTE thread.
The following change is proposed in the
Hi Jagane,
since you did not explicitly cast a -1 or other numerical vote, please if
you wish go ahead and cast a vote in the VOTE thread.
Best regards,
--Matt
On Tue, May 21, 2013 at 3:47 PM, Jagane Sundar jag...@sundar.org wrote:
I see one significant benefit to having Release Plan votes:
+1 (binding). I think it's important to maintain the release continuity,
otherwise we could end up with the 0.20.2 / 0.20.200 problem all over again
(parallel stable dev tracks without a parent-child relationship to each
other, ie with disjoint subsets of functionality). I consider achieving a
Arun, not sure whether your Yes to all already covered this, but I'd
like
to throw in support for the compatibility guidelines being a blocker.
+1 to that. Definitely an overriding concern for me.
On Wed, May 15, 2013 at 1:25 PM, Sandy Ryza sandy.r...@cloudera.com wrote:
+1 (non-binding)
lets fork this thread into the appropriate ML and discuss the practical,
achievable
steps that can be included into the release criteria of Hadoop 2.0.5-beta
Seems to me common-dev is the appropriate ML, and Arun has invited Jiras to
include.
Open a Jira with your suggested list, and we carry
Roman, what is your model for how test results from Bigtop should feed back
into Hadoop-2 development?
With the understanding that (a) software does have bugs, and (b) you're not
going to get an SLA on community-sponsored software,
what are your ideas for how to close the loop better?
Would CI
I'm actually drafting such a proposal. Will open the discussion as a
[PROPOSAL] in general@
--Matt
On Wed, May 15, 2013 at 4:44 PM, Arun C Murthy a...@hortonworks.com wrote:
On May 15, 2013, at 3:27 PM, Chris Douglas wrote:
+1 (binding) on the proposal.
However, the value we get from
-1.2.0-bin.tar.gz is missing the source code and can't be built.
-C
On Mon, May 6, 2013 at 11:11 AM, Matt Foley ma...@apache.org wrote:
Hi all,
I have posted the signed tarballs for Hadoop 1.2.0-rc1 at
http://people.apache.org/~mattf/hadoop-1.2.0-rc1/
Release notes
, May 13, 2013 at 1:32 PM, Matt Foley mfo...@hortonworks.com wrote:
Hi Chris,
Unless I screwed up my build, hadoop-1.2.0.tar.gz includes the built
artifacts as well as full buildable source and docs.
Hadoop-1.2.0-bin.tar.gz is intended to contain only the built artifacts
(binaries
to track down a reference, but
I'm pretty sure on this one... source-only is OK. Some have argued
it's the only acceptable form. -C
On Mon, May 13, 2013 at 1:36 PM, Matt Foley ma...@apache.org wrote:
The vote passed and we have accepted Hadoop version 1.2.0 for release:
+1 binding: 4 (1 slightly
clarification that the prohibition is against binaries for
which we don't also distribute source, so (AFAICT) distributing
third-party jars is also not kosher. I'll ask for clarification. -C
On Mon, May 13, 2013 at 2:44 PM, Matt Foley mfo...@hortonworks.com
wrote:
Hmm. My understanding
13, 2013 at 5:35 PM, Matt Foley mfo...@hortonworks.com
wrote:
Thanks for the reference.
Roy's email clearly says that the thing to be voted on should be source
only. This email is in the context of a discussion about a release
candidate that incorporated jars (from a third-party project
[
https://issues.apache.org/jira/browse/HADOOP-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley reopened HADOOP-9504:
Reopened for submission to branch-1.2, per email from [~jlowe] on common-dev@,
Sun, May 12, 2013
Lowe jl...@yahoo-inc.com wrote:
Matt, would you consider adding HADOOP-9504 to the release? Some groups
using HBase have been bitten by this bug and would like to see it in a 1.x
release.
Jason
On 05/10/2013 11:44 AM, Matt Foley wrote:
Hi all,
just a reminder this vote is underway
Hi all,
just a reminder this vote is underway and will close Monday 11:30am.
Please review and vote!
Thanks,
--Matt
On Mon, May 6, 2013 at 11:36 AM, Matt Foley ma...@apache.org wrote:
Friends,
Nexus issues are resolved, and the Nexus staging repository for Hadoop
1.2.0-rc1 properly uploaded
Hi all,
I have posted the signed tarballs for Hadoop 1.2.0-rc1 at
http://people.apache.org/~mattf/hadoop-1.2.0-rc1/
Release notes are at:
releasenotes_1.2.0-rc1.htmlhttp://people.apache.org/~mattf/hadoop-1.2.0-rc1/releasenotes_1.2.0-rc1.html
I'm having a little trouble with Nexus (it seems to
Friends,
Nexus issues are resolved, and the Nexus staging repository for Hadoop
1.2.0-rc1 properly uploaded. Thanks for your patience.
--Matt
On Mon, May 6, 2013 at 11:11 AM, Matt Foley ma...@apache.org wrote:
Hi all,
I have posted the signed tarballs for Hadoop 1.2.0-rc1 at
http
[
https://issues.apache.org/jira/browse/HADOOP-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-9375.
Resolution: Fixed
Port HADOOP-7290 to branch-1 to fix TestUserGroupInformation failure
On Fri, Mar 15, 2013 at 9:53 PM, Robert Evans ev...@yahoo-inc.com wrote:
+1
On 3/10/13 10:38 PM, Matt Foley ma...@apache.org wrote:
Hi all,
I have created branch-1.2 from branch-1, and propose to cut the first
release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow
,dir/subdir) can lose all data in the source
directory
https://issues.apache.org/jira/browse/HADOOP-9261
I think that should be one to pick up -it and the extended test are still
be reviewed
On 4 February 2013 12:39, Matt Foley ma...@apache.org wrote:
Hi,
this weekend I propose to create
the requirements.
Thank you,
--Matt
On Sun, Mar 3, 2013 at 12:16 PM, Konstantin Shvachko
shv.had...@gmail.comwrote:
Didn't I explain in details what I am asking for?
Thanks,
--Konst
On Sun, Mar 3, 2013 at 11:08 AM, Matt Foley mfo...@hortonworks.com
wrote:
Hi Konstantin,
I'd like to point out two
Thanks. I agree Windows -1's in test-patch should not block commits.
--Matt
On Mon, Mar 4, 2013 at 2:30 PM, Konstantin Shvachko shv.had...@gmail.comwrote:
On Mon, Mar 4, 2013 at 12:22 PM, Matt Foley mfo...@hortonworks.com
wrote:
Konstantine, you have voted -1, and stated some
Matt Foley created HADOOP-9359:
--
Summary: Add Windows build and unit test to test-patch pre-commit
testing
Key: HADOOP-9359
URL: https://issues.apache.org/jira/browse/HADOOP-9359
Project: Hadoop Common
on the merge.
I am glad we agreed.
Having Jira to track the CI effort is a good idea.
Thanks,
--Konstantin
On Mon, Mar 4, 2013 at 3:29 PM, Matt Foley mfo...@hortonworks.com wrote:
Thanks. I agree Windows -1's in test-patch should not block commits.
--Matt
On Mon, Mar 4, 2013
Added to the Jira to modify http://wiki.apache.org/hadoop/HowToContribute to
document this decision.
On Mon, Mar 4, 2013 at 5:42 PM, Harsh J ha...@cloudera.com wrote:
Thanks Suresh. Regarding where; we can state it on
http://wiki.apache.org/hadoop/HowToContribute in the test-patch
section
...@gmail.comwrote:
Hi Matt,
On Sat, Mar 2, 2013 at 12:32 PM, Matt Foley mfo...@hortonworks.com
wrote:
Konstantin,
I would like to explore what it would take to remove this perceived
impediment --
Glad you decided to explore. Thank you.
although I reserve the right to argue
+1 (binding)
Apache is supposed to be about the community. We have here a community of
developers, who have actively and openly worked to add a major improvement
to Hadoop: the ability to work cross-platform. Furthermore, the size of
the substantive part of the needed patch is only about 1500
, Arun C Murthy a...@hortonworks.com wrote:
+1 (binding)
Downloaded bits, verified sigs and ran examples on a single-node cluster.
Arun
On Feb 14, 2013, at 2:57 PM, Matt Foley wrote:
REMINDER: VOTING CLOSES TONIGHT AT 10PM.
Happy St. Valentine's Day :-)
--Matt
On Thu, Feb 14
there. Or, we should have another SRC TARBALL as we do have in Hadoop2
which is nothing but the whole (buildable) source.
Cheers
On Fri, Feb 8, 2013 at 1:46 PM, Matt Foley ma...@apache.org wrote:
official release artifacts MUST be source artifacts
That's why the release is tagged in SVN
REMINDER: VOTING CLOSES TONIGHT AT 10PM.
Happy St. Valentine's Day :-)
--Matt
On Thu, Feb 14, 2013 at 2:56 PM, Matt Foley ma...@apache.org wrote:
Hi, I peeled open the non-binary tarball (http://people.apache.org/~
mattf/hadoop-1.1.2-rc5/hadoop-1.1.2.tar.gz), and besides the complete
src
code, not builds...
-C
On Thu, Jan 31, 2013 at 7:13 PM, Matt Foley ma...@apache.org wrote:
(resending with modified Subject line for RC5)
Hadoop-1.1.2-rc4 is withdrawn.
Hadoop-1.1.2-rc5 is available at
http://people.apache.org/~mattf/hadoop-1.1.2-rc5/
or in SVN at
http
, and it worked. Since that change touched
checkpointing, I also verified that the 2NN could complete a successful
checkpoint.
I'll also verify the PGP signature once I track down the public key that
was used for signing.
Thank you,
--Chris
On Thu, Jan 31, 2013 at 7:13 PM, Matt Foley ma
[
https://issues.apache.org/jira/browse/HADOOP-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-8418.
Resolution: Fixed
Fix UGI for IBM JDK running on Windows
:
Checkpoint exception causes fatal damage to fsimage? I have uploaded a
patch, and I expect to receive a code review in the next day or two.
Thank you,
--Chris
On Mon, Jan 28, 2013 at 3:32 PM, Matt Foley mfo...@hortonworks.com
wrote:
A new build of Hadoop-1.1.2 is available at
http
A new build of Hadoop-1.1.2 is available at
http://people.apache.org/~mattf/hadoop-1.1.2-rc4/
or in SVN at
http://svn.apache.org/viewvc/hadoop/common/tags/release-1.1.2-rc4/
or in the Maven repo.
This candidate for a stabilization release of the Hadoop-1.1 branch has 23
patches and several
[
https://issues.apache.org/jira/browse/HADOOP-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley reopened HADOOP-8419:
GzipCodec NPE upon reset with IBM JDK
[
https://issues.apache.org/jira/browse/HADOOP-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley reopened HADOOP-8418:
Since successfully committed to branch-1.1, changed fixVersion from 1.2.0 to
1.1.2.
However, re
[
https://issues.apache.org/jira/browse/HADOOP-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-9132.
Resolution: Fixed
Contradictory information on Hadoop releases webpage
Hi,
sorry for the thrash, but further testing in a whole-stack situation with
Hive over Hadoop-1.1.1, exposed bug
HADOOP-9115https://issues.apache.org/jira/browse/HADOOP-9115,
Deadlock in configuration when writing configuration to hdfs. This bug
did not previously manifest during Hadoop-1.1.1
, Matt Foley ma...@apache.org wrote:
No, but it speaks to whether the Hadoop bylaws can extend the Apache
voting
procedures and draw finer distinctions. For example, the Apache voting
procedures only identify 3 types of votable issue, while the Hadoop
bylaws
identify 9 types of votable
[
https://issues.apache.org/jira/browse/HADOOP-8924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley reopened HADOOP-8924:
After discussion in common-dev@, the community consensus rejected use of
Python. (see references
would be almost there.
this would leave the tar stitching, which is done as script to handle SO
symlinks. though i have and idea on how we could take care of it.
i'll be creating a jira momentarily.
thx
Alejandro
On Dec 4, 2012, at 12:28 PM, Matt Foley mfo...@hortonworks.com wrote
, which I'd argue it should leave outside of
Hadoop)
Thx
On Mon, Nov 26, 2012 at 1:16 PM, Giridharan Kesavan
gkesa...@hortonworks.com wrote:
+1, +1, +1
-Giri
On Sat, Nov 24, 2012 at 12:13 PM, Matt Foley ma...@apache.org wrote:
For discussion, please see previous thread
in the current build, besides saveVersion.sh, you see as
candidate to be migrated to Phyton?
* How are you planning to define what Phyton modules can be used? Will
developers have to install them manually?
Cheers
On Thu, Nov 29, 2012 at 2:39 PM, Matt Foley mfo...@hortonworks.com
wrote
to be migrated to Phyton?
* How are you planning to define what Phyton modules can be used? Will
developers have to install them manually?
Cheers
On Thu, Nov 29, 2012 at 2:39 PM, Matt Foley mfo...@hortonworks.com
wrote:
Hi Alejandro,
Please see in-line below.
On Mon, Nov 26
and have seen no problems.
Sorry for not noticing this earlier in the VOTE.
-andy
On Tue, Nov 27, 2012 at 9:45 AM, Matt Foley mfo...@hortonworks.com
wrote:
Thanks for noticing these, Tom.
--Matt
On Tue, Nov 27, 2012 at 4:59 AM, Tom White t...@cloudera.com wrote:
+1 Signatures
For discussion, please see previous thread [PROPOSAL] introduce Python as
build-time and run-time dependency for Hadoop and throughout Hadoop stack.
This vote consists of three separate items:
1. Contributors shall be allowed to use Python as a platform-independent
scripting language for
[
https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-6453.
Resolution: Fixed
Hadoop wrapper script shouldn't ignore an existing JAVA_LIBRARY_PATH
to release 1.1.0, with no backward
incompatibilities.
I took the opportunity to assure that all branch-1.0 changes are in 1.1.1,
and all branch-1.1 changes are in branch-1.
The jira database has been made consistent.
Please vote. Voting will end on Tuesday 27 Nov., at 2:05pm PST.
Thank you,
--Matt Foley
to
additional high-priority patches if they are reliable and can be committed
to branch-1.1 by the code freeze date. Let's try to stick to serious bugs
and not new features. Thanks!
--Matt Foley
Release Manager
HADOOP-8823. ant package target should not depend on cn-docs. (szetszwo
:
+1 (non-binding)
Downloaded and installed from tar file and ran dfsio read/write tests on a
single-node cluster. Tests ran successfully.
Thanks,
Arpit
On Fri, Oct 5, 2012 at 2:31 PM, Matt Foley ma...@apache.org wrote:
Here at long last is a votable release candidate for Hadoop 1.1.0
With a vote of 5 binding +1's, 2 non-binding +1's, and no -1's, the vote
for Hadoop-1.0.4 passes.
I am in process of publishing it, and will then announce to general@.
Thank you,
--Matt
On Wed, Oct 10, 2012 at 8:57 AM, Matt Foley ma...@apache.org wrote:
Please vote. Vote on 1.0.4-rc0 closes
Please vote. Vote on 1.0.4-rc0 closes tomorrow. Vote on 1.1.0-rc5 closes
Friday.
Thank you,
--Matt
On Thu, Oct 4, 2012 at 1:59 PM, Matt Foley ma...@apache.org wrote:
Hi,
There has been a request from several PMC members for a maintenance
release of hadoop-1.0.
Please download and test
Hi Eli,
Thanks for the suggestion. Looks like this has gotten fleshed out a little
more since I started doing releases.
I've had my key posted at MIT since the beginning. I've now also uploaded
it to the PGP Global Directory, and uploaded the key fingerprint to my
profile at id.apache.org.
://people.apache.org/~mattf/hadoop-1.1.0-rc5/releasenotes.html
Vote will run for 1 week as usual, terminating at 2:30pm PDT, Fri 12 Oct
2012.
Thank you,
--Matt Foley
Release Manager
://people.apache.org/~mattf/hadoop-1.0.4-rc0/releasenotes.html
Vote will run for 1 week as usual, terminating at 2pm PDT, Thur 11 Oct 2012.
Thank you,
--Matt Foley
Release Manager
Status check: Wanted to let the community know I am working on the release
candidate and hope to have it posted tomorrow. Have to clear some unit
test failures.
Thanks,
--Matt
Thanks, Gopal.
On Mon, Oct 1, 2012 at 5:14 PM, Gopal V go...@hortonworks.com wrote:
On 10/1/12 11:46 AM, Matt Foley wrote:
Status check: Wanted to let the community know I am working on the release
candidate and hope to have it posted tomorrow. Have to clear some unit
test failures
.
Initially, I didn't recommend them since I thought 1.1 was too close, but
since these (MR-3837 MR-4328 etc.) are well-baked at this point (deployed
at multiple places) I'd like to include them in.
thanks,
Arun
thanks,
Arun
On Sep 24, 2012, at 9:58 PM, Matt Foley wrote:
Okay.
On Mon
Datanode drops OS cache behind reads even for short reads
MAPREDUCE-1906 default minimum heartbeat
MAPREDUCE-3289 use fadvise
I will spin a new RC with these fixes, and hope to offer it for vote by
Wednesday.
Thanks,
--Matt
On Wed, Sep 19, 2012 at 1:09 PM, Matt Foley ma...@apache.org wrote
Okay.
On Mon, Sep 24, 2012 at 7:05 PM, Uma Maheswara Rao G
hadoop@gmail.comwrote:
Hi Matt,
Good to include HDFS-3701 also. I set the fixed versions as 1.1.0 as well.
Regards,
Uma
On Tue, Sep 25, 2012 at 7:29 AM, Matt Foley ma...@apache.org wrote:
Hi all,
Since the Review RC went
The RC has been uploaded to Nexus / maven.
--Matt
On Mon, Sep 17, 2012 at 6:46 PM, Matt Foley ma...@apache.org wrote:
Hi,
Please review this release candidate for Hadoop-1.1.0. As suggested
before, I am posting it for review, and will start a vote on it if it
passes the next week
Hi,
Please review this release candidate for Hadoop-1.1.0. As suggested
before, I am posting it for review, and will start a vote on it if it
passes the next week with no serious issues being found.
Tarballs, rpms, and debs are available at
http://people.apache.org/~mattf/hadoop-1.1.0-rc4/
Hi Slavik,
Unfortunately I have not finished a release 1.1.0 of Hadoop yet, although
there is a 1.1.0-rc2 that is not too bad. A built version (both developer
tarballs and bigtop-style rpms) is available at
http://people.apache.org/~mattf/hadoop-1.1.0-rc2/
I'm having a few unit test
Matt Foley created HADOOP-8612:
--
Summary: Backport HADOOP-8599 to branch-1 (Non empty response when
read beyond eof)
Key: HADOOP-8612
URL: https://issues.apache.org/jira/browse/HADOOP-8612
Project
it today.
I am working on the content of 0.3.1 BigTop release and will shortly
post the
vote for it. Once Hadoop 1.1 rc is cut we'll start testing it with the
rest of
the stack.
Cos
On Fri, Jul 06, 2012 at 02:24PM, Matt Foley wrote:
Hi Cos,
the query string didn't come thru
[
https://issues.apache.org/jira/browse/HADOOP-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-8166.
Resolution: Duplicate
Remove JDK 1.5 dependency from building forrest docs
1 - 100 of 196 matches
Mail list logo
