You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2019/07/16 16:42:12 UTC
[jira] [Updated] (SPARK-24814) Relationship between catalog and
datasources
[ https://issues.apache.org/jira/browse/SPARK-24814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-24814:
----------------------------------
Affects Version/s: (was: 2.4.0)
3.0.0
> Relationship between catalog and datasources
> --------------------------------------------
>
> Key: SPARK-24814
> URL: https://issues.apache.org/jira/browse/SPARK-24814
> Project: Spark
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Bruce Robbins
> Priority: Major
>
> This is somewhat related, though not identical to, [~rdblue]'s SPIP on datasources and catalogs.
> Here are the requirements (IMO) for fully implementing V2 datasources and their relationships to catalogs:
> # The global catalog should be configurable (the default can be HMS, but it should be overridable).
> # The default catalog (or an explicitly specified catalog in a query, once multiple catalogs are supported) can determine the V2 datasource to use for reading and writing the data.
> # Once multiple catalogs are supported, a user should be able to specify a catalog on spark.read and df.write operations. As specified above, The catalog would determine the datasource to use for the read or write operation.
> Old #3:
> -Conversely, a V2 datasource can determine which catalog to use for resolution (e.g., if the user issues {{spark.read.format("acmex").table("mytable")}}, the acmex datasource would decide which catalog to use for resolving “mytable”).-
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org