No worries :)

On Sat, Mar 21, 2020 at 2:47 PM leesf <[email protected]> wrote:

> sorry pratyaksh, it may mainly for chinese developers. :)
>
> Pratyaksh Sharma <[email protected]> 于2020年3月20日周五 下午6:05写道:
>
> > Cannot follow it properly due to language issues. :)
> >
> > On Fri, Mar 20, 2020 at 3:05 PM leesf <[email protected]> wrote:
> >
> > > PDF is now available. Please check it out.
> > >
> > > Using Apache Hudi to build the next-generation data lake and its
> > > application in medical big data
> > > https://drive.google.com/open?id=1dmH2kWJF69PNdifPp37QBgjivOHaSLDn
> > >
> > > Building a near real-time, high-performance data warehouse based on
> > Apache
> > > Hudi and Apache Kylin
> > > https://drive.google.com/open?id=1Pk_WdFxfEZxMMfAOn0R8-m3ALkcN6G9e
> > >
> > > Vinoth Chandar <[email protected]> 于2020年3月12日周四 下午2:31写道:
> > >
> > > > This is awesome.. Please be sure to add the talk to our website page
> as
> > > > well once the slides are up!
> > > >
> > > >
> > > >
> > > > On Wed, Mar 11, 2020 at 4:27 AM vino yang <[email protected]>
> > wrote:
> > > >
> > > > > Hi Leesf,
> > > > >
> > > > > Thanks for sharing this news.
> > > > >
> > > > > Glad to hear this and it's great to see Hudi being further promoted
> > in
> > > > > China.
> > > > >
> > > > > Best,
> > > > > Vino
> > > > >
> > > > > leesf <[email protected]> 于2020年3月11日周三 下午7:21写道:
> > > > >
> > > > > > Hudi users & developers,
> > > > > >
> > > > > > There will be an online Hudi Meetup this week (Mar. 14).
> Engineers
> > > from
> > > > > > DXY.cn(丁香园), Tencent(腾讯), ClinBrain (柯林布瑞), and Kyligence will
> > share
> > > > > their
> > > > > > use cases and experiences with Apache Kylin & Apache Hudi.
> > > > > >
> > > > > > Date: Mar. 14
> > > > > > Time: 7:00 PM - 9:00 PM  (UTC+08:00)
> > > > > > Language: Chinese
> > > > > > Activity Form: live video streaming
> > > > > > Fee: Free!
> > > > > > Link for Registration:
> > > > https://mp.weixin.qq.com/s/KOCZNhInrJNDLXp5nD9V2w
> > > > > >
> > > > > > Best,
> > > > > > Leesf
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to