You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Ruan Pearce-Authers (Jira)" <ji...@apache.org> on 2021/03/20 22:14:00 UTC
[jira] [Created] (ARROW-12037) [Rust] [DataFusion] Support catalogs
and schemas for table namespacing
Ruan Pearce-Authers created ARROW-12037:
-------------------------------------------
Summary: [Rust] [DataFusion] Support catalogs and schemas for table namespacing
Key: ARROW-12037
URL: https://issues.apache.org/jira/browse/ARROW-12037
Project: Apache Arrow
Issue Type: New Feature
Components: Rust - DataFusion
Reporter: Ruan Pearce-Authers
Assignee: Ruan Pearce-Authers
Proposal doc: [https://docs.google.com/document/d/1_bCP_tjVRLJyOrMBOezSFNpF0hwPa1ZS_qMWv1uvtS4/edit?usp=sharing]
Summary from the doc:
This is a particularly messy aspect of most SQL implementations, so let’s settle on some terms first:
* Schema: a collection of named tables
* Catalog: a collection of named schemas (also known as a database)
This doc will attempt to describe a standards-compliant implementation for DataFusion, using Postgres’ design decisions as a guide where the standard is not prescriptive (due to our adoption of its query dialect).
As an example of how this works in practice, given a default catalog of “db” and a default schema of “public”, all these table references would be equivalent:
* db.public.my_table
* public.my_table
* my_table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)