Got it, thanks for the correction.
JVS
On Feb 3, 2011, at 4:56 PM, Alex Boisvert wrote:
> Hi John,
>
> Just to clarify where I was going with my line of questioning. There's no
> Apache policy that prevents dependencies on incubator project, whether it's
> releases, snapshots or even home-m
On Feb 3, 2011, at 5:09 PM, Alan Gates wrote:
> Are you referring to the serde jar or any particular serde's we are making
> use of?
Both (see below).
JVS
[jsichi@dev1066 ~/open/howl/howl/howl/src/java/org/apache/hadoop/hive/howl] ls
cli/ common/ data/ mapreduce/ pig/ rcfile/
[jsic
Are you referring to the serde jar or any particular serde's we are
making use of?
Alan.
On Feb 3, 2011, at 4:30 PM, John Sichi wrote:
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:
Hi John,
Just to clarify where I was going with my line of questioning. There's no
Apache policy that prevents dependencies on incubator project, whether it's
releases, snapshots or even home-made hacked-together packaging of an
incubator project.It's been done before and as long as the incu
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 e
I was going off of what I read in HADOOP-3676 (which lacks a reference as
well). But I guess if a release can be made from the incubator, then it's not
a blocker.
JVS
On Feb 3, 2011, at 3:29 PM, Alex Boisvert wrote:
> On Thu, Feb 3, 2011 at 11:38 AM, John Sichi wrote:
> Besides the fact that
On Thu, Feb 3, 2011 at 11:38 AM, John Sichi wrote:
> Besides the fact that the refactoring required is significant, I don't
> think this is possible to do quickly since:
>
> 1) Hive (unlike Pig) requires a metastore
>
> 2) Hive releases can't depend on an incubator project
>
I'm not sure what yo
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/
What I am referring to is metastore/ dir of hive, part of hive code
which howl cares about most. Other howl code is for additional
functionalities that Howl provides (none of which lives in metastore/
dir) they are in howl/ dir. There are few build file changes, but they
are trivial.
Ashutosh
On T
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
> commi
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 wrote:
> I am interested in some numbers
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 wrote:
> Hey,
>
>>
>> If we do go ahead with pulling the metastore ou
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 lov
Besides the fact that the refactoring required is significant, I don't think
this is possible to do quickly since:
1) Hive (unlike Pig) requires a metastore
2) Hive releases can't depend on an incubator project
It's worth pointing out that Howl is already using Hive's CLI+DDL (not just
metasto
Food for thought, what if the metastore were moved to Howl more
aggressively? It seems like the end state everyone's aiming for is
that Hive and Pig share Howl as a metastore layer, which makes all
kinds of sense.. would it increase the chances of long term success
if you guys just went for it an
+1
On Wed, Feb 2, 2011 at 13:18, Alan Gates wrote:
> Howl is a table management system built to provide metadata and storage
> management across data processing tools in Hadoop (Pig, Hive, MapReduce,
> ...). You can learn more details at http://wiki.apache.org/pig/Howl. For
> the last six month
Alan,
I see your points. I agree with you and I am +1.
(incubator/subproject is not important to me)
You mentioned that hive is cautious about checking changes into the
meta-store. I would not say we (hive) are cautious. Hive is getting
pulled in many people in many directions (this is a goo
On Thu, Feb 3, 2011 at 12:16 AM, Alan Gates wrote:
> Edward,
>
> I understand your concern with having a copy of the metastore code in Howl.
> However, let's separate code from governance. The reason Howl has a copy
> of Hive's metastore is not because we're proposing it for the Incubator, it
>
Edward,
I understand your concern with having a copy of the metastore code in
Howl. However, let's separate code from governance. The reason Howl
has a copy of Hive's metastore is not because we're proposing it for
the Incubator, it is because in the course of developing it over the
las
On Wed, Feb 2, 2011 at 5:08 PM, Jeff Hammerbacher wrote:
> Awesome! Huge +1.
>
> On Wed, Feb 2, 2011 at 1:18 PM, Alan Gates wrote:
>
>> Howl is a table management system built to provide metadata and storage
>> management across data processing tools in Hadoop (Pig, Hive, MapReduce,
>> ...). You
20 matches
Mail list logo
