hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Sichi <jsi...@fb.com>
Subject Re: [VOTE] Sponsoring Howl as an Apache Incubator project
Date Fri, 04 Feb 2011 00:30:51 GMT
I forgot about the serde dependencies...can you add those to the Initial Source note in [[HowlProposal]]
just for completeness?

JVS

On Feb 3, 2011, at 3:11 PM, Alan Gates wrote:

> Yes, it adds Input and Output formats for MapReduce and load and store functions for
Pig.  In the future it we expect it will continue to add more additional layers.
> 
> Alan.
> 
> On Feb 3, 2011, at 2:49 PM, John Sichi wrote:
> 
>> But Howl does layer on some additional code, right?
>> 
>> https://github.com/yahoo/howl/tree/howl/howl
>> 
>> JVS
>> 
>> On Feb 3, 2011, at 1:49 PM, Ashutosh Chauhan wrote:
>> 
>>> There are none as of today. In the past, whenever we had to have
>>> changes, we do it in a separate branch in Howl and once those get
>>> committed to hive repo, we pull it over in our trunk and drop the
>>> branch.
>>> 
>>> Ashutosh
>>> On Thu, Feb 3, 2011 at 13:41, yongqiang he <heyongqiangict@gmail.com> wrote:
>>>> I am interested in some numbers around the lines of code changes (or
>>>> files of changes) which are in Howl but not in Hive?
>>>> Can anyone give some information here?
>>>> 
>>>> Thanks
>>>> Yongqiang
>>>> On Thu, Feb 3, 2011 at 1:15 PM, Jeff Hammerbacher <hammer@cloudera.com>
wrote:
>>>>> Hey,
>>>>> 
>>>>>> 
>>>>>> If we do go ahead with pulling the metastore out of Hive, it might
make
>>>>>> most sense for Howl to become its own TLP rather than a subproject.
>>>>> 
>>>>> Yes, I did not read the proposal closely enough. I think an end state
as a
>>>>> TLP makes more sense for Howl than as a Pig subproject. I'd really love
to
>>>>> see Howl replace the metastore in Hive and it would be more natural to
do so
>>>>> as a TLP than as a Pig subproject--especially since the current Howl
>>>>> repository is literally a fork of Hive.
>>>>> 
>>>>>> 
>>>>>> In the incubator proposal, we have mentioned these issues, but we've
>>>>>> attempted to avoid prejudicing any decision.  Instead, we'd like
to assess
>>>>>> the pros and cons (including effort required and impact expected)
for both
>>>>>> approaches as part of the incubation process.
>>>>> 
>>>>> Glad the issues are being considered.
>>>>> Later,
>>>>> Jeff
>>>> 
>> 
> 


Mime
View raw message