You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Ximo Guanter (JIRA)" <ji...@apache.org> on 2018/11/24 16:22:00 UTC
[jira] [Created] (SPARK-26160) Make assertNotBucketed call in
DataFrameWriter::save optional
Ximo Guanter created SPARK-26160:
------------------------------------
Summary: Make assertNotBucketed call in DataFrameWriter::save optional
Key: SPARK-26160
URL: https://issues.apache.org/jira/browse/SPARK-26160
Project: Spark
Issue Type: Improvement
Components: SQL
Affects Versions: 2.4.0
Reporter: Ximo Guanter
Currently, the `.save` method in DataFrameWriter will fail if the dataframe is bucketed and/or sorted. This makes sense, since there is no way of storing metadata in the current file-based data sources to know whether a file was bucketed or not.
I have a use case where I would like to implement a new, file-based data source which could keep track of that kind of metadata, so I would like to be able to `.save` bucketed dataframes.
Would a patch to extend the datasource api with an indicator of whether that source is able to serialize bucketed dataframes be a welcome addition? I'm happy to work on it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org