Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm proposing.
Please vote, the vote will the usual period of 7 days.
thanks,
Arun
[main]$ svn diff
Index:
+1
Tom
On 6/24/14, 3:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm proposing.
Please vote, the vote will the usual period of 7 days.
+1
On Tue, Jun 24, 2014 at 6:42 AM, Thomas Graves
tgra...@yahoo-inc.com.invalid wrote:
+1
Tom
On 6/24/14, 3:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've
+1
Thanks
Devaraj K
On Tue, Jun 24, 2014 at 2:23 PM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm proposing.
Please vote, the vote will
+1 (non-binding)
Deployed in a two node cluster and ran few M/R Jobs, everything works fine.
On Thu, Jun 19, 2014 at 8:44 PM, Thomas Graves
tgra...@yahoo-inc.com.invalid wrote:
Hey Everyone,
There have been various bug fixes that have went into
branch-0.23 since the 0.23.10 release.
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1811/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 35040 lines...]
Running
+1 (binding)
-Sandy
On Tue, Jun 24, 2014 at 7:53 AM, Devaraj K deva...@apache.org wrote:
+1
Thanks
Devaraj K
On Tue, Jun 24, 2014 at 2:23 PM, Arun C Murthy a...@hortonworks.com
wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes
+1 (non-binding)
On Tue, Jun 24, 2014 at 8:54 AM, Jason Lowe jl...@yahoo-inc.com.invalid
wrote:
+1 (binding)
Jason
On 06/24/2014 03:53 AM, Arun C Murthy wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've
+1 (binding)
— Hitesh
On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm proposing.
Please vote, the vote will
+1(non-binding)
On Wed, Jun 25, 2014 at 1:55 AM, Hitesh Shah hit...@apache.org wrote:
+1 (binding)
— Hitesh
On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote:
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com
wrote:
Folks,
As discussed, I'd like to call a vote on
+1 (non-binding)
(2014/06/24 10:33), Zhijie Shen wrote:
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote:
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com
wrote:
Folks,
+1 (binding)
On Tue, Jun 24, 2014 at 10:33 AM, Zhijie Shen zs...@hortonworks.com wrote:
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote:
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 24, 2014 at 1:53 AM, Arun
+1 (binding)
Chris Nauroth
Hortonworks
http://hortonworks.com/
On Tue, Jun 24, 2014 at 10:58 AM, Jakob Homan jgho...@gmail.com wrote:
+1 (binding)
On Tue, Jun 24, 2014 at 10:33 AM, Zhijie Shen zs...@hortonworks.com
wrote:
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron
+1 -C
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm proposing.
Please vote, the vote will the usual
+1
On Tue, Jun 24, 2014 at 11:13 AM, Chris Douglas cdoug...@apache.org wrote:
+1 -C
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com
wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've
Hi David,
UserGroupInformation.createRemoteUser does not attach credentials to the
returned ugi. I expect the server side is rejecting the connection due to
lack of credentials. This is actually by design. The
UserGroupInformation.createRemoteUser method is primarily intended for use
on the
Andrew,
Thanks for starting this thread. I'll edit the wiki to provide more context
around rolling-upgrades etc. which, as I pointed out in the original thread,
are key IMHO.
On Jun 24, 2014, at 11:17 AM, Andrew Wang andrew.w...@cloudera.com wrote:
That classpath policy was explicitly added because we can't lock down our
dependencies for security/bug fix reasons, and also because if we do update
something explicitly, their transitive dependencies can change -beyond our
control.
https://issues.apache.org/jira/browse/HADOOP-9555 is an example
Tx for the new thread Andrew, hopefully it can attract more eyes.
Here's what I am behind - a modified proposal C.
- Overall I wouldn't think about EOL of JDK7 and/or JDK8 specifically given
how long it has taken for JDK6 life-cycle to end. We should try to focus on
JDK7 only for now.
- As we
While we haven't codified this in our compatibility guidelines, dropping a
Java version seems to me like change that needs to happen alongside a major
release. In plain talk, it has the ability to break everything for users
who aren't doing anything particularly unreasonable.
I don't think we
Hi all,
On dependencies, we've bumped library versions when we think it's safe and
the APIs in the new version are compatible. Or, it's not leaked to the app
classpath (e.g the JUnit version bump). I think the JIRAs Arun mentioned
fall into one of those categories. Steve can do a better job
+1, though I think 2.5 may be premature if we want to send a warning note
last ever. That's an issue for followon when in branch 2.
Guava and protobuf.jar are two things we have to leave alone, with the
first being unfortunate, but their attitude to updates is pretty dramatic.
The latter? We all
On Jun 24, 2014, at 4:22 PM, Andrew Wang andrew.w...@cloudera.com wrote:
Since Hadoop apps can and do depend on the Hadoop classpath, the classpath
is effectively part of our API. I'm sure there are user apps out there that
will break if we make incompatible changes to the classpath. I
Zhijie Shen created MAPREDUCE-5940:
--
Summary: Avoid negative elapsed time in JHS/MRAM web UI and
services
Key: MAPREDUCE-5940
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5940
Project:
26 matches
Mail list logo
