argh, gmail trying to be extra smart collapsed his comment on that and i 
missed. sorry

thx 

Alejandro
(phone typing)

> On Jan 9, 2014, at 9:23, larry mccay <lmc...@apache.org> wrote:
> 
> Hi Alejandro -
> 
> I believe that Steve has already acknowledged that a package rename is
> required and that the project is likely not appropriate for Hadoop proper.
> 
> thanks,
> 
> --larry
> 
> 
> On Thu, Jan 9, 2014 at 11:46 AM, Alejandro Abdelnur <t...@cloudera.com>wrote:
> 
>> I may have not been clear enough, I was referring to using
>> 'org.apache.hadoop' as package prefix for a project other than hadoop.
>> 
>> Thanks
>> 
>> 
>> On Thu, Jan 9, 2014 at 8:36 AM, Benson Margulies <bimargul...@gmail.com
>>> wrote:
>> 
>>> If you can work out a plan to do this directly in Hadoop, there's no
>>> need for the incubator. You just build and and contribute it in
>>> cahoots with them, and earn commit over there as you go.
>>> 
>>> On Thu, Jan 9, 2014 at 11:14 AM, Alejandro Abdelnur <t...@cloudera.com>
>>> wrote:
>>>> Mmmh, if i recall correctly this has come up in the past with other
>>> projects and it was decided against it. Could you please check with the
>>> hadoop folks about it?
>>>> 
>>>> Thx
>>>> 
>>>>> On Jan 9, 2014, at 1:19 AM, Steve Loughran <ste...@hortonworks.com>
>>> wrote:
>>>>> 
>>>>> no its wrong, it should all be under org.apache.hoya.
>>>>> 
>>>>> I had the hadoop prefix so that I could perhaps put it straight into
>> the
>>>>> hadoop code as another tools module -no need for incubation. But as
>> the
>>>>> actual providers and all tests are related to the deployment of hbase
>>> and
>>>>> accumulo, it really comes downstream of those.
>>>>> 
>>>>> so a rename is needed.
>>>>> 
>>>>> but yes, ASF headers everywhere
>>>>> 
>>>>> 
>>>>>> On 8 January 2014 22:48, Henry Saputra <henry.sapu...@gmail.com>
>>> wrote:
>>>>>> 
>>>>>> I like how the initial code already put under "
>>>>>> org.apache.hadoop.hoya"  with correct ASF header =)
>>>>>> 
>>>>>> - Henry
>>>>>> 
>>>>>> On Wed, Jan 8, 2014 at 7:08 AM, Steve Loughran <
>> ste...@hortonworks.com
>>>> 
>>>>>> wrote:
>>>>>>> I'm starting to put together the incubation proposal for Hoya: a
>> tool
>>> to
>>>>>>> dynamically deploy applications such as HBase or Accumulo on YARN
>>>>>>> 
>>>>>>> https://wiki.apache.org/incubator/HoyaProposal
>>>>>>> 
>>>>>>> It does already work to the extent that it can bring up either
>>>>>> application,
>>>>>>> run different clusters of different versions, and remember where
>>>>>> containers
>>>>>>> were allocated so that on application restart it can ask for them
>>> back.
>>>>>>> That increases data locality and makes a big difference with HBase.
>>>>>>> 
>>>>>>> It also needs a lot more work -YARN-896 is adding YARN features that
>>>>>> help,
>>>>>>> but there's lots of fun to be had in Hoya including
>>>>>>> -leading edge work in failure handling, modelling cluster
>>> unreliability
>>>>>>> and reacting to it. Can we move beyond simple blacklisting to
>>>>>>> "greylisting", accepting unreliable boxes if we have no altenatives
>>>>>>> 
>>>>>>> Then there's adding more providers, to support different application
>>>>>>> installations -I'm starting to write a functional test framework
>> which
>>>>>> need
>>>>>>> provider-specific workload generations
>>>>>>> 
>>>>>>> Other features: AM should have a web ui that redirects to the live
>>>>>>> endpoints to all the app-specific UIs (e.g. HBase Master GUI), as
>>> well as
>>>>>>> displaying cluster state itself, for people and for management
>>> tools....
>>>>>>> 
>>>>>>> To summarise: lots of fun to be had
>>>>>>> 
>>>>>>> -steve
>>>>>>> 
>>>>>>> --
>>>>>>> CONFIDENTIALITY NOTICE
>>>>>>> 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.
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>>> --
>>>>> CONFIDENTIALITY NOTICE
>>>>> 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.
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
>> --
>> Alejandro
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to