You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2019/03/25 22:08:00 UTC
[jira] [Resolved] (SPARK-27256) If the configuration is used to set
the number of bytes, we'd better use `bytesConf`'.
[ https://issues.apache.org/jira/browse/SPARK-27256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-27256.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 24187
[https://github.com/apache/spark/pull/24187]
> If the configuration is used to set the number of bytes, we'd better use `bytesConf`'.
> --------------------------------------------------------------------------------------
>
> Key: SPARK-27256
> URL: https://issues.apache.org/jira/browse/SPARK-27256
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core, SQL
> Affects Versions: 3.0.0
> Reporter: liuxian
> Assignee: liuxian
> Priority: Minor
> Fix For: 3.0.0
>
>
> Currently, if we want to configure `spark. sql. files. maxPartitionBytes` to 256 megabytes, we must set `spark. sql. files. maxPartitionBytes=268435456`, which is very unfriendly to users.
> And if we set it like this:`spark. sql. files. maxPartitionBytes=256M`, we will encounter this exception:
> _Exception in thread "main" java.lang.IllegalArgumentException: spark.sql.files.maxPartitionBytes should be long, but was 256M_
> _at org.apache.spark.internal.config.ConfigHelpers$.toNumber(ConfigBuilder.scala:34)_
--
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