You mean {common,mapreduce,yarn,hdfs}-{dev,commits,issues}@hadoop.apache.org
lists mentioned on https://hadoop.apache.org/mailing_lists.html ?
On Friday, May 16, 2014 4:44 PM, Pete of Pete wrote:
On behalf of those of us who keep an eye on posts for commercial reasons
(but do not contribute
Cheers Aaron!
All the best,
;-pete
On 16 May 2014 19:47, "Aaron T. Myers" wrote:
> Hey Pete,
>
> The "contributor list" we're referring to is just the collection of folks
> in JIRA that JIRAs can be assigned to. It doesn't impact anyone's ability
> to follow JIRAs, just have new JIRAs assigned
Nemon Lou created HADOOP-10613:
--
Summary: Potential Resource Leaks in FileSystem.CACHE
Key: HADOOP-10613
URL: https://issues.apache.org/jira/browse/HADOOP-10613
Project: Hadoop Common
Issue Typ
Hi all,
I saw HDFS-6421 float by, which made me wonder what versions of Linux we
support. The FAQ (http://wiki.apache.org/hadoop/FAQ) just says "Linux", but
clearly we need a version cut off somewhere.
I looked at a few vendor sites for the oldest supported RHEL version for
their branch-2 based d
[
https://issues.apache.org/jira/browse/HADOOP-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe reopened HADOOP-10474:
-
Reopening this as Hive is an important part of the Hadoop stack. Arguably we
shouldn't remove som
Hey Pete,
The "contributor list" we're referring to is just the collection of folks
in JIRA that JIRAs can be assigned to. It doesn't impact anyone's ability
to follow JIRAs, just have new JIRAs assigned to them. It also doesn't do
anything to JIRAs that are already assigned.
--
Aaron T. Myers
So
I removed a bunch who have been inactive for years a couple of months ago
from hdfs. Having a limit forces us to remove stale entries, so it is not
entirely bad. If the actual number of contributors reach the limit and
the limit can't be changed easily, we might be able to create another jira
gro
Brandon Li created HADOOP-10612:
---
Summary: NFS failed to refresh the user group id mapping table
Key: HADOOP-10612
URL: https://issues.apache.org/jira/browse/HADOOP-10612
Project: Hadoop Common
On behalf of those of us who keep an eye on posts for commercial reasons
(but do not contribute) Is there the option of setting up a list that
accesses the dev comms, but doesn't impact the contributor list?
P
On Wed, May 14, 2014 at 4:31 AM, Suresh Srinivas wrote:
> Last time we cleaned up nam
[
https://issues.apache.org/jira/browse/HADOOP-10588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved HADOOP-10588.
-
Resolution: Fixed
Fix Version/s: 2.5.0
0.23.11
Hadoop Flags: Revi
Alejandro Abdelnur created HADOOP-10611:
---
Summary: KeyVersion name should not be assumed to be the 'key name
@ the version number"
Key: HADOOP-10611
URL: https://issues.apache.org/jira/browse/HADOOP-10611
ASF JIRA has been moving to role-based over group-based security -you may
be able to give more people a role than a group allows. But, as of last
week and a spark-initiated change, by default contributors can't assign
issues.
someone could talk to infra@apache and see if a move would help
On 14
12 matches
Mail list logo
