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

Reply via email to