+1.

- Chinmay.

On 3 Oct 2016 7:25 a.m., "Amol Kekre" <[email protected]> wrote:

> Ananth,
> This would be great to have. +1
>
> Thks
> Amol
>
> On Sun, Oct 2, 2016 at 8:38 AM, Munagala Ramanath <[email protected]>
> wrote:
>
> > +1
> >
> > Kudu looks impressive from the overview, though it seems to still be
> > maturing.
> >
> > Ram
> >
> >
> > On Sat, Oct 1, 2016 at 11:42 PM, ananth <[email protected]> wrote:
> >
> > > Hello All,
> > >
> > > I was wondering if it would be worthwhile for the community to consider
> > > support for Apache Kudu as a store ( as a contrib operator inside
> Apache
> > > Malhar ) .
> > >
> > > Here are some benefits I see:
> > >
> > > 1. Kudu is just declared 1.0 and has just been declared production
> ready.
> > > 2. Kudu as a store might a good a fit for many architectures in the
> > >    years to come because of its capabilities to provide mutability of
> > >    data ( unlike HDFS ) and optimized storage formats for scans.
> > > 3. It seems to also withstand high-throughput write patterns which
> > >    makes it a stable sink for Apex workflows which operate at very high
> > >    volumes.
> > >
> > >
> > > Here are some links
> > >
> > >  *  From the recent Strata conference
> > >    https://kudu.apache.org/2016/09/26/strata-nyc-kudu-talks.html
> > >  * https://kudu.apache.org/overview.html
> > >
> > > I can implement this operator if the community feels it is worth adding
> > it
> > > to our code base. If so, could someone please assign the JIRA to me. I
> > have
> > > created this JIRA to track this : https://issues.apache.org/jira
> > > /browse/APEXMALHAR-2278
> > >
> > >
> > > Regards,
> > >
> > > Ananth
> > >
> > >
> >
>

Reply via email to