[
https://issues.apache.org/jira/browse/ARROW-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lamb resolved ARROW-12037.
---------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 9762
[https://github.com/apache/arrow/pull/9762]
> [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
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> 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)
