-
Notifications
You must be signed in to change notification settings - Fork 28.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-12682][SQL] Add support for (optionally) not storing tables in hive metadata format #10826
Conversation
Test build #49664 has finished for PR 10826 at commit
|
@@ -323,7 +323,15 @@ private[hive] class HiveMetastoreCatalog(val client: ClientInterface, hive: Hive | |||
|
|||
// TODO: Support persisting partitioned data source relations in Hive compatible format | |||
val qualifiedTableName = tableIdent.quotedString | |||
val skipHiveMetadata = options.getOrElse("skip_hive_metadata", "false").toBoolean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about skipHiveMetadata
?
Thanks @yhuai, all comments addressed. |
test this please |
jenkins test this please |
Test build #50014 has finished for PR 10826 at commit
|
test this please |
Test build #50040 has finished for PR 10826 at commit
|
LGTM. Merging to master and branch 1.6. |
… hive metadata format This PR adds a new table option (`skip_hive_metadata`) that'd allow the user to skip storing the table metadata in hive metadata format. While this could be useful in general, the specific use-case for this change is that Hive doesn't handle wide schemas well (see https://issues.apache.org/jira/browse/SPARK-12682 and https://issues.apache.org/jira/browse/SPARK-6024) which in turn prevents such tables from being queried in SparkSQL. Author: Sameer Agarwal <sameer@databricks.com> Closes #10826 from sameeragarwal/skip-hive-metadata. (cherry picked from commit 08c781c) Signed-off-by: Yin Huai <yhuai@databricks.com>
This PR adds a new table option (
skip_hive_metadata
) that'd allow the user to skip storing the table metadata in hive metadata format. While this could be useful in general, the specific use-case for this change is that Hive doesn't handle wide schemas well (see https://issues.apache.org/jira/browse/SPARK-12682 and https://issues.apache.org/jira/browse/SPARK-6024) which in turn prevents such tables from being queried in SparkSQL.