[
https://issues.apache.org/jira/browse/HADOOP-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley reassigned HADOOP-6077:
---
Assignee: Giridharan Kesavan
> test-patch target does not validate that forrest docs are bui
Doug, given Owen's away this week, can you update the Jira config to
implement (4). Until this is done, the patch testing process can't
see when Jira's change states and thus nothing is getting tested.
Thanks,
Nige
Begin forwarded message:
From: Hemanth Yamijala
Date: June 24, 2009 9:55:
+1 for (4)
On 6/23/09 8:33 PM, "Owen O'Malley" wrote:
I really prefer the current approach, but clearly we need to reach
consensus. Last week we had a case where a developer sent to the users
lists because he thought that dev was reserved for jira traffic. That
is a bad sign. Doug is the most p
[
https://issues.apache.org/jira/browse/HADOOP-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley resolved HADOOP-5898.
-
Resolution: Fixed
Fix Version/s: site
I just committed this. Thanks Corinne!
> Hadoop T
+1 for (4).
Jim Kellerman (POWERSET) wrote:
+1 for (4)
-Original Message-
From: Doug Cutting [mailto:cutt...@gmail.com] On Behalf Of Doug Cutting
Sent: Tuesday, June 23, 2009 11:32 AM
To: core-dev@hadoop.apache.org
Subject: Re: more information about project split
Owen O'Malley wro
[
https://issues.apache.org/jira/browse/HADOOP-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhiyong zhang updated HADOOP-5851:
--
Attachment: HADOOP-5851.patch
remove find-bug warnings.
> proxy to call LDAP for IP lookup an
[
https://issues.apache.org/jira/browse/HADOOP-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated HADOOP-6104:
Summary: Tests in oah.record are silently broken or are potentially broken
(was: Tests in oah.rec
Tests in oah.record are silently broken or potentially are potentially broken
-
Key: HADOOP-6104
URL: https://issues.apache.org/jira/browse/HADOOP-6104
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhiyong zhang updated HADOOP-5851:
--
Attachment: HADOOP-5851.patch
corrected several typos and changed several places for code opti
[
https://issues.apache.org/jira/browse/HADOOP-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhiyong zhang updated HADOOP-5851:
--
Attachment: HADOOP-5851.patch
1. removed System.setProperty. Use Keymanagers and TrustManagers
[
https://issues.apache.org/jira/browse/HADOOP-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723738#action_12723738
]
Jiaqi Tan commented on HADOOP-5073:
---
I would like to propose that a particular subset of
+1 for (4)
> -Original Message-
> From: Doug Cutting [mailto:cutt...@gmail.com] On Behalf Of Doug Cutting
> Sent: Tuesday, June 23, 2009 11:32 AM
> To: core-dev@hadoop.apache.org
> Subject: Re: more information about project split
>
> Owen O'Malley wrote:
> > I think the community is bette
+1 on (4)
I want to see all updates to the project without browsing the jira,
which is not particularly friendly for tracking latest changes.
And email filters worked well for me if I need to filter anything out.
--Konstantin
Jim Kellerman (POWERSET) wrote:
+1 for (4)
-Original Message---
+1 for (4)
> -Original Message-
> From: Doug Cutting [mailto:cutt...@gmail.com] On Behalf Of Doug Cutting
> Sent: Tuesday, June 23, 2009 11:32 AM
> To: core-dev@hadoop.apache.org
> Subject: Re: more information about project split
>
> Owen O'Malley wrote:
> > I think the community is bette
Amr Awadallah wrote:
I can't set email filters for which jiras I am interested in getting
full updates on, that would mean I have to set an additional filter
for each jira ticket one by one, not very scalable. Is that what you
suggesting?
I think all that Dhruba is suggesting is that if a dev
What I use to filter mails for jiras I am more interested in
(watching/created/assigned...) :
from : j...@apache.org
to : rang...@yahoo-inc.com
hope it helps.
Raghu.
Amr Awadallah wrote:
Dhruba,
I can't set email filters for which jiras I am interested in getting
full updates on, that wo
+1 for (4)
On Tue, Jun 23, 2009 at 10:47 PM, Dhruba Borthakur
wrote:
+1 for (4).
This means that the default settings for a hadoop developer is to get
eveyrthing via email. This allows anyone to set filter settings on
his/her
own email reader to prioritise which types of emails one woul
Dhruba,
I can't set email filters for which jiras I am interested in getting
full updates on, that would mean I have to set an additional filter
for each jira ticket one by one, not very scalable. Is that what you
suggesting?
On 6/23/09, Dhruba Borthakur wrote:
> +1 for (4).
>
> This means th
[
https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anjali M updated HADOOP-6035:
-
Attachment: hadoop-hadoop-tasktracker-anjus.in.log.2009-06-24
> jobtracker stops when namenode goes out
[
https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723599#action_12723599
]
Anjali M commented on HADOOP-6035:
--
I tried that too. But still the problem persists. Two
[
https://issues.apache.org/jira/browse/HADOOP-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amareshwari Sriramadasu reassigned HADOOP-6090:
---
Assignee: Amareshwari Sriramadasu
> GridMix is broke after upgrading
[
https://issues.apache.org/jira/browse/HADOOP-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723486#action_12723486
]
Amareshwari Sriramadasu commented on HADOOP-6103:
-
defaultResources is a p
[
https://issues.apache.org/jira/browse/HADOOP-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723481#action_12723481
]
Amareshwari Sriramadasu commented on HADOOP-4975:
-
bq. I made the change t
Configuration clone constructor does not clone all the members.
---
Key: HADOOP-6103
URL: https://issues.apache.org/jira/browse/HADOOP-6103
Project: Hadoop Common
Issue Type: Bug
24 matches
Mail list logo
