hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@hortonworks.com>
Subject Re: [Proposal] Pluggable Namespace
Date Mon, 07 Oct 2013 19:42:59 GMT

Milind/Andrew and everyone else,

Didn't know an innocuous question regarding a technical issue can blow up so much.

I asked a technical question. If you have an answer and you want to respond, please do so.
If you don't have an answer, you can reply so. Otherwise please keep this thread for the technical
discussions of the proposal.

If you have other non-technical concerns, fork this thread and participate in that. Even then,
I think the dev lists are for discussing technical matters, we can all try to keep it that


On Oct 7, 2013, at 12:05 PM, Andrew Purtell wrote:

> Hi Doug,
> I recognize some of what we recently experienced on a HDFS matter in what
> Milind wrote even if this was not the appropriate forum for it. Odd mention
> of "conspiracy theories" aside, for people who may come to this thread
> later, perhaps you can recommend an appropriate public Apache community
> forum for discussing such concerns?
> On Mon, Oct 7, 2013 at 11:15 AM, Doug Cutting <cutting@apache.org> wrote:
>> On Sun, Oct 6, 2013 at 5:58 PM, Milind Bhandarkar
>> <mbhandarkar@gopivotal.com> wrote:
>>> Is Hortonworks concerned that this proposal conflicts with their
>>> development on federated namenode ?
>> This question might better be asked directly of folks at Hortonworks
>> rather than here.
>> Let's please not dwell on such aspects here, keeping this discussion
>> technical.
>> Thanks,
>> Doug
> -- 
> Best regards,
>   - Andy
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message