[jira] [Assigned] (SPARK-33561) distinguish table properties and options in V2 catalog API
[ https://issues.apache.org/jira/browse/SPARK-33561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-33561: --- Assignee: Ryan Blue > distinguish table properties and options in V2 catalog API > -- > > Key: SPARK-33561 > URL: https://issues.apache.org/jira/browse/SPARK-33561 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.1.0 >Reporter: Wenchen Fan >Assignee: Ryan Blue >Priority: Major > Fix For: 3.1.0 > > > Right now, user-specified table properties and options are merged and passed > to `TableCatalog.createTable` as table properties, because v2 catalog does > not have the table options concept. > We need to distinguish table properties and options if we want to use v2 > catalog API to implement hive catalog. We can add an `option.` prefix to > table options when merging it into table properties. For backward > compatibility, we can also merge the original table options without the > `option.` prefix into table properties as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-33561) distinguish table properties and options in V2 catalog API
[ https://issues.apache.org/jira/browse/SPARK-33561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33561: Assignee: Apache Spark > distinguish table properties and options in V2 catalog API > -- > > Key: SPARK-33561 > URL: https://issues.apache.org/jira/browse/SPARK-33561 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.1.0 >Reporter: Wenchen Fan >Assignee: Apache Spark >Priority: Major > > Right now, user-specified table properties and options are merged and passed > to `TableCatalog.createTable` as table properties, because v2 catalog does > not have the table options concept. > We need to distinguish table properties and options if we want to use v2 > catalog API to implement hive catalog. We can add an `option.` prefix to > table options when merging it into table properties. For backward > compatibility, we can also merge the original table options without the > `option.` prefix into table properties as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-33561) distinguish table properties and options in V2 catalog API
[ https://issues.apache.org/jira/browse/SPARK-33561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33561: Assignee: (was: Apache Spark) > distinguish table properties and options in V2 catalog API > -- > > Key: SPARK-33561 > URL: https://issues.apache.org/jira/browse/SPARK-33561 > Project: Spark > Issue Type: Improvement > Components: SQL >Affects Versions: 3.1.0 >Reporter: Wenchen Fan >Priority: Major > > Right now, user-specified table properties and options are merged and passed > to `TableCatalog.createTable` as table properties, because v2 catalog does > not have the table options concept. > We need to distinguish table properties and options if we want to use v2 > catalog API to implement hive catalog. We can add an `option.` prefix to > table options when merging it into table properties. For backward > compatibility, we can also merge the original table options without the > `option.` prefix into table properties as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
