Hi,

> +1 for the material page. Can we link it off community.html?

Yes, good idea.

I have created an issue to track this work.[1]

[1]: https://issues.apache.org/jira/browse/HUDI-216

Vinoth Chandar <[email protected]> 于2019年8月21日周三 下午8:35写道:

> +1 for the material page. Can we link it off community.html?
>
> @Semantic Beeng <[email protected]> , that seems like technical
> documentation on cwiki. Will track that work as well.
>
> On Tue, Aug 20, 2019 at 11:43 PM vino yang <[email protected]> wrote:
>
> > Hi guys,
> >
> > Glad to see you all agree with this proposal.
> >
> > The talk is in Chinese, mainly talk about Tencent's Flink platform, and
> > of course, there are several pages about Data Lake and Hudi. Therefore, I
> > don't know if it is appropriate to put it on the Hudi official website.
> >
> > I'd like to create a material page to put those logo images stored in
> > Google Drive into this page so that other peoples can easily find them.
> >
> > What do you think? Do you agree with this idea?
> >
> > Best,
> > Vino
> >
> >
> > Bhavani Sudha Saktheeswaran <[email protected]> 于2019年8月21日周三
> > 上午1:59写道:
> >
> > > +1 I think this is great idea to showcase Hudi.
> > >
> > > Thanks,
> > > Sudha
> > >
> > > On Tue, Aug 20, 2019 at 4:02 AM vino yang <[email protected]>
> wrote:
> > >
> > > > Hi guys,
> > > >
> > > > I am going to give a talk about Hudi in a meetup.
> > > > However, I can not find the material and resource of Hudi, for
> example,
> > > > logo images with(or without) text and icons.
> > > >
> > > > IMHO, it would be good to put these files on the official web site.
> > Here
> > > is
> > > > a good example.[1]
> > > >
> > > > What do you think?
> > > >
> > > > Best,
> > > > Vino
> > > >
> > > > [1]:
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__flink.apache.org_material.html&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=oyPDRKU5b-LuEWWyf8gacx4mFFydIGdyS50OKdxizX0&m=-1N33JCyNCJF5bt2p2fut6LPCAYogvgH8pA_Z2rnx-E&s=cVSiVUfLTdIal89tKzI3CRmjLR89RVqvl-spAfelptQ&e=
> > > >
> > >
> >
>

Reply via email to