Hi Martin. I don't see any conflicts between that and any current or near-term work I know of happening in Kudu. There are a couple of related JIRAs for database support: KUDU-2063 <https://issues.apache.org/jira/browse/KUDU-2063> and KUDU-2362 <https://issues.apache.org/jira/browse/KUDU-2362>.
In fact, Impala does something similar right now. Kudu tables managed by Impala are named like impala::database_name.table_name. It might also be a good idea to add some kind of identifier like the initial "impala::" for presto-managed or -created tables, since many other integrations may use a database_name.table_name convention. -Will On Tue, Apr 24, 2018 at 7:01 PM, Martin Weindel <martin.wein...@gmail.com> wrote: > Hi, > > are there any plans for supporting schemas in the sense of relational > databases, i.e. namespaces of tables? > > I'm asking, as I have a discussion in the Presto project for the proposed > Kudu connector. (see https://github.com/prestodb/presto/pull/10388) > > As Presto supports catalog > schema > table, I thought it a good idea to > make use of these namespaces of tables also in the Kudu connector. > > This happens by using a dot in the Kudu table name. E.g. the Kudu table > name "mytable" is mapped to kudu.default.mytable in Presto and a Kudu > table named "myschema.mytable2" to kudu.myschema.mytable2. There is nothing > in Kudu which prevents using table names with dots, so it does not seem to > be a problem at least at the moment. > > Can someone of the Kudu developer team can give me a hint, if you see any > conflicts with the Kudu roadmap? > > Thanks, > > Martin Weindel > >
