Subject: [DISCUSS] Identifiers with multi-catalog support


Thanks for writing this up. Just to show why option 1 is not sufficient. MySQL and Postgres are the two most popular open source database systems, and both support database → schema → table 3 part identification, so Spark supporting only 2 part name passing to the data source (option 1) isn't sufficient.

For the issues you brought up w.r.t. nesting - what's the challenge in supporting it? I can also see us not supporting it for now (no nesting allowed, leaf - 1 level can only contain leaf tables), and adding support for nesting in the future.

On Sun, Jan 13, 2019 at 1:38 PM, Ryan Blue < [EMAIL PROTECTED]lid > wrote: