You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Anton Kedin <ke...@google.com> on 2019/06/14 23:14:24 UTC
[SQL] Let's split the TableProvider
Hi dev@, and especially anyone interested in SQL,
We have an interface called TableProvider (and some other related classes)
in Beam SQL that manages how we resolve the table schemas, construct IOs
and do other related and unrelated things when parsing the queries. At the
moment it feels very overloaded and not easy to use or extend. I propose we
split it into few more abstractions. Here's an initial draft doc for
discussion, let me know what you think:
https://docs.google.com/document/d/1QAPz74XMctCsiUnutWR1ejEXjKGmpSQJ61qtfAiBE4E
Regards,
Anton
Re: [SQL] Let's split the TableProvider
Posted by Ismaël Mejía <ie...@gmail.com>.
Can you please add this to the design documents webpage.
https://beam.apache.org/contribute/design-documents/
On Wed, Jun 19, 2019 at 6:36 AM Kenneth Knowles <ke...@apache.org> wrote:
>
> Nice doc. I really appreciate how it gives an overview of the code.
>
> Kenn
>
> On Fri, Jun 14, 2019 at 4:14 PM Anton Kedin <ke...@google.com> wrote:
>>
>> Hi dev@, and especially anyone interested in SQL,
>>
>> We have an interface called TableProvider (and some other related classes) in Beam SQL that manages how we resolve the table schemas, construct IOs and do other related and unrelated things when parsing the queries. At the moment it feels very overloaded and not easy to use or extend. I propose we split it into few more abstractions. Here's an initial draft doc for discussion, let me know what you think:
>> https://docs.google.com/document/d/1QAPz74XMctCsiUnutWR1ejEXjKGmpSQJ61qtfAiBE4E
>>
>> Regards,
>> Anton
>>
>>
>>
>>
Re: [SQL] Let's split the TableProvider
Posted by Kenneth Knowles <ke...@apache.org>.
Nice doc. I really appreciate how it gives an overview of the code.
Kenn
On Fri, Jun 14, 2019 at 4:14 PM Anton Kedin <ke...@google.com> wrote:
> Hi dev@, and especially anyone interested in SQL,
>
> We have an interface called TableProvider (and some other related classes)
> in Beam SQL that manages how we resolve the table schemas, construct IOs
> and do other related and unrelated things when parsing the queries. At the
> moment it feels very overloaded and not easy to use or extend. I propose we
> split it into few more abstractions. Here's an initial draft doc for
> discussion, let me know what you think:
>
> https://docs.google.com/document/d/1QAPz74XMctCsiUnutWR1ejEXjKGmpSQJ61qtfAiBE4E
>
> Regards,
> Anton
>
>
>
>
>