Based on my understanding, we are not inventing anything new here.
Basically, we are building a federated database system especially after we
supporting multiple catalog. There are many mature commercial products in
the market. For example,
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5
Hi Ryan,
Thanks for hosting the discussion! I think the table catalog is super
useful, but since this is the first time we allow users to extend catalog,
it's better to write down some details from end-user APIs to internal
management.
1. How would end-users register/unregister catalog with SQL AP
Your history isn't really accurate. Years before Spark became an Apache
project, the AMPlab and UC Berkeley placed the Spark code under a 3-clause
BSD License and made the code publicly available. Later, a group of
developers and Spark users from both inside and outside Berkeley brought
Spark and t
