+1 to both.
- milind
---
Milind Bhandarkar
On 1/29/13 4:16 PM, "Prasad Mujumdar" wrote:
> Measure 1: +1 (non binding)
> Measure 2: +1 (non binding)
>
>thanks
>Prasad
>
>On Tue, Jan 29, 2013 at 2:57 PM, Shreepadma Venugopalan <
>shreepa...@cloudera.com> wrote:
>
>> Measure 1: +1
>> Measure
+1.
Putting my marketing hat on (I don¹t think marketeers is a four-letter
word), touting Hive metastore as a sufficient metadata solution for other
platforms such as MR and Pig, is nothing to be ashamed of.
- Milind
---
Milind Bhandarkar
Chief Scientist,
Machine Learning Platforms,
Greenplum, A
I am really looking forward to the headline that "Hive Metastore now
provides metadata for platforms other than Hive".
I think that would demonstrate the flexibility of Hive metastore to the
world.
Even if some people consider this a purely "marketing message", the
flexibility of the APIs do appe
r to automatically promote them to
>full committer status on the Hive project.
>
>On Thu, Dec 20, 2012 at 1:10 PM, Bhandarkar, Milind <
>milind.bhandar...@emc.com> wrote:
>
>> I agree with Ashish.
>>
>> When Hcat becomes a subproject of Hive, all Hcat commi
I agree with Ashish.
When Hcat becomes a subproject of Hive, all Hcat committers should
immediately become Hive committers.
After all, that worked well for Hadoop, where all Hadoop committers can
commit to all Hadoop code (common/HDFS/MapReduce), but not all do, instead
focusing only on their are
