Vadim Bondarev created HDFS-4528:
Summary: Cover package org.apache.hadoop.yarn with unit tests
Key: HDFS-4528
URL: https://issues.apache.org/jira/browse/HDFS-4528
Project: Hadoop HDFS
Issue
On Sat, Feb 23, 2013 at 4:23 PM, Tsz Wo Sze wrote:
> I still do not see a valid reason to remove HDFS-2246 immediately. Some
> users may have insecure clusters and they don't want to change their
> configuration.
Because it doesn't make sense to support multiple mechanisms for the
same thing.
On Sat, Feb 23, 2013 at 4:23 PM, Tsz Wo Sze wrote:
> I still do not see a valid reason to remove HDFS-2246 immediately. Some
> users may have insecure clusters and they don't want to change their
> configuration.
>
> BTW, is Unix Domain Socket supported by all Unix-like systems? Does anyone
>
That sounds like a good plan to me.
--
Aaron T. Myers
Software Engineer, Cloudera
On Sat, Feb 23, 2013 at 6:11 PM, Andrew Wang wrote:
> Taking silence here to mean we aren't that concerned with the javadocs.
>
> Are we okay with Doug's proposed fix for the broken links?
>
> Thanks,
> Andrew
>
Done. I added the redirect so that link is no longer broken.
Doug
On Mon, Feb 25, 2013 at 11:19 AM, Aaron T. Myers wrote:
> That sounds like a good plan to me.
>
>
> --
> Aaron T. Myers
> Software Engineer, Cloudera
>
>
> On Sat, Feb 23, 2013 at 6:11 PM, Andrew Wang wrote:
>
>> Taking silence h
[
https://issues.apache.org/jira/browse/HDFS-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved HDFS-4520.
--
Resolution: Fixed
Fix Version/s: Snapshot (HDFS-2802)
Hadoop Flags: R
I agree that HDFS-2246 is a short term solution and we should not keep it there
forever. However, we still need a transition period to replace an old
mechanism by a new one. No?
Tsz-Wo
From: Eli Collins
To: "hdfs-dev@hadoop.apache.org" ; Tsz Wo Sze
Sen
I think we need a transition period when any kinks are worked out of
347 but I don't think we need one alpha/beta release where both
mechanisms are supported (because 2246 was just a short term solution
rather than a long term commitment). Ideally we'd get 347 in branch-2
for 2.0.4-beta and have t
On Mon, Feb 25, 2013 at 1:16 PM, Eli Collins wrote:
> I think we need a transition period when any kinks are worked out of
> 347 but I don't think we need one alpha/beta release where both
> mechanisms are supported (because 2246 was just a short term solution
> rather than a long term commitment)
On Mon, Feb 25, 2013 at 1:50 PM, Chris Douglas wrote:
> On Mon, Feb 25, 2013 at 1:16 PM, Eli Collins wrote:
>> I think we need a transition period when any kinks are worked out of
>> 347 but I don't think we need one alpha/beta release where both
>> mechanisms are supported (because 2246 was just
[
https://issues.apache.org/jira/browse/HDFS-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved HDFS-4514.
--
Resolution: Fixed
Fix Version/s: Snapshot (HDFS-2802)
I have committed th
ATM's suggestion of removing HDFS-2246 in trunk, but not branch-2, is
> a rational compromise: it allows some period for others to adapt, but
> not an indefinite one. It's not clear what you're proposing, if
> anything.
>
I am not sure why a release that supports both these is such a bad idea.
A
On Mon, Feb 25, 2013 at 4:09 PM, Suresh Srinivas wrote:
> ATM's suggestion of removing HDFS-2246 in trunk, but not branch-2, is
>> a rational compromise: it allows some period for others to adapt, but
>> not an indefinite one. It's not clear what you're proposing, if
>> anything.
>>
>
>
>
> I am n
Tsz Wo (Nicholas), SZE created HDFS-4529:
Summary: Decide the semantic of concat with snapshots
Key: HDFS-4529
URL: https://issues.apache.org/jira/browse/HDFS-4529
Project: Hadoop HDFS
Liang Xie created HDFS-4530:
---
Summary: return buffer into direct bufferPool in BlockReaderLocal
as possible
Key: HDFS-4530
URL: https://issues.apache.org/jira/browse/HDFS-4530
Project: Hadoop HDFS
15 matches
Mail list logo
