You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Ingo Bürk <in...@ververica.com> on 2021/06/10 11:45:17 UTC
[DISCUSS] FLIP-129 (Update): Registering sources/sinks on Table API
without SQL
Hello everyone,
we would like to pick up work on FLIP-129 which aims to improve the Table
API by supporting the creation of sources / sinks without having to go
through SQL/DDL. This FLIP was approved a while ago, and some things have
changed since then. We'd like to propose a few changes, see [1], before
starting work on it.
Our proposal is mainly motivated by reducing the scope in some parts to
improve maintainability and relying more on ConfigOptions being the single
source of truth. We also want to expose this functionality for
non-temporary tables.
We'd like to open this for discussion to collect any feedback. Once the
discussion has stabilized I'll update the FLIP itself and start a new vote.
[1]
https://docs.google.com/document/d/1tpirvF0u723QF005UrgdbvF-Tp0Jbg_qhlbda4mk7Ck/edit?usp=sharing
Regards
Ingo
Re: [DISCUSS] FLIP-129 (Update): Registering sources/sinks on Table
API without SQL
Posted by Ingo Bürk <in...@ververica.com>.
Thanks everyone for the feedback! Since there haven't been any
questions/discussions, I'll be moving this to a vote thread next week.
Regards
Ingo
On Tue, Jun 15, 2021 at 5:36 PM JING ZHANG <be...@gmail.com> wrote:
> Thanks Ingo for starting this discussion.
>
>
>
> Big +1 for this feature. Looking forward to the feature.
>
>
> Best regards,
> JING ZHANG
>
> Jark Wu <im...@gmail.com> 于2021年6月15日周二 下午3:48写道：
>
> > Thanks Ingo for picking up this FLIP.
> >
> > FLIP-129 is an important piece to have a complete Table SQL story,
> > and users have been waiting for a long time. Let's finish it in this
> > release!
> > Your proposed changes look good to me.
> >
> > I also cc'd people who voted in previous FLIP-129.
> >
> > Best,
> > Jark
> >
> > On Thu, 10 Jun 2021 at 19:46, Ingo Bürk <in...@ververica.com> wrote:
> >
> > > Hello everyone,
> > >
> > > we would like to pick up work on FLIP-129 which aims to improve the
> Table
> > > API by supporting the creation of sources / sinks without having to go
> > > through SQL/DDL. This FLIP was approved a while ago, and some things
> have
> > > changed since then. We'd like to propose a few changes, see [1], before
> > > starting work on it.
> > > Our proposal is mainly motivated by reducing the scope in some parts to
> > > improve maintainability and relying more on ConfigOptions being the
> > single
> > > source of truth. We also want to expose this functionality for
> > > non-temporary tables.
> > >
> > > We'd like to open this for discussion to collect any feedback. Once the
> > > discussion has stabilized I'll update the FLIP itself and start a new
> > vote.
> > >
> > > [1]
> > >
> > >
> >
> https://docs.google.com/document/d/1tpirvF0u723QF005UrgdbvF-Tp0Jbg_qhlbda4mk7Ck/edit?usp=sharing
> > >
> > >
> > > Regards
> > > Ingo
> > >
> >
>
Re: [DISCUSS] FLIP-129 (Update): Registering sources/sinks on Table
API without SQL
Posted by JING ZHANG <be...@gmail.com>.
Thanks Ingo for starting this discussion.
Big +1 for this feature. Looking forward to the feature.
Best regards,
JING ZHANG
Jark Wu <im...@gmail.com> 于2021年6月15日周二 下午3:48写道：
> Thanks Ingo for picking up this FLIP.
>
> FLIP-129 is an important piece to have a complete Table SQL story,
> and users have been waiting for a long time. Let's finish it in this
> release!
> Your proposed changes look good to me.
>
> I also cc'd people who voted in previous FLIP-129.
>
> Best,
> Jark
>
> On Thu, 10 Jun 2021 at 19:46, Ingo Bürk <in...@ververica.com> wrote:
>
> > Hello everyone,
> >
> > we would like to pick up work on FLIP-129 which aims to improve the Table
> > API by supporting the creation of sources / sinks without having to go
> > through SQL/DDL. This FLIP was approved a while ago, and some things have
> > changed since then. We'd like to propose a few changes, see [1], before
> > starting work on it.
> > Our proposal is mainly motivated by reducing the scope in some parts to
> > improve maintainability and relying more on ConfigOptions being the
> single
> > source of truth. We also want to expose this functionality for
> > non-temporary tables.
> >
> > We'd like to open this for discussion to collect any feedback. Once the
> > discussion has stabilized I'll update the FLIP itself and start a new
> vote.
> >
> > [1]
> >
> >
> https://docs.google.com/document/d/1tpirvF0u723QF005UrgdbvF-Tp0Jbg_qhlbda4mk7Ck/edit?usp=sharing
> >
> >
> > Regards
> > Ingo
> >
>
Re: [DISCUSS] FLIP-129 (Update): Registering sources/sinks on Table
API without SQL
Posted by Jark Wu <im...@gmail.com>.
Thanks Ingo for picking up this FLIP.
FLIP-129 is an important piece to have a complete Table SQL story,
and users have been waiting for a long time. Let's finish it in this
release!
Your proposed changes look good to me.
I also cc'd people who voted in previous FLIP-129.
Best,
Jark
On Thu, 10 Jun 2021 at 19:46, Ingo Bürk <in...@ververica.com> wrote:
> Hello everyone,
>
> we would like to pick up work on FLIP-129 which aims to improve the Table
> API by supporting the creation of sources / sinks without having to go
> through SQL/DDL. This FLIP was approved a while ago, and some things have
> changed since then. We'd like to propose a few changes, see [1], before
> starting work on it.
> Our proposal is mainly motivated by reducing the scope in some parts to
> improve maintainability and relying more on ConfigOptions being the single
> source of truth. We also want to expose this functionality for
> non-temporary tables.
>
> We'd like to open this for discussion to collect any feedback. Once the
> discussion has stabilized I'll update the FLIP itself and start a new vote.
>
> [1]
>
> https://docs.google.com/document/d/1tpirvF0u723QF005UrgdbvF-Tp0Jbg_qhlbda4mk7Ck/edit?usp=sharing
>
>
> Regards
> Ingo
>