You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/09/11 16:30:00 UTC
[jira] [Resolved] (SPARK-25221) [DEPLOY] Consistent trailing
whitespace treatment of conf values
[ https://issues.apache.org/jira/browse/SPARK-25221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin resolved SPARK-25221.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0
Issue resolved by pull request 22213
[https://github.com/apache/spark/pull/22213]
> [DEPLOY] Consistent trailing whitespace treatment of conf values
> ----------------------------------------------------------------
>
> Key: SPARK-25221
> URL: https://issues.apache.org/jira/browse/SPARK-25221
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 2.3.1
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Priority: Major
> Fix For: 2.4.0
>
>
> When you use a custom line delimiter {{spark.hadoop.textinputformat.record.delimiter}} that has a leading or a trailing whitespace character it's only possible when specified via {{--conf}} . Our pipeline consists of a highly customized generated jobs. Storing all the config in a properities file is not only better for readability but even necessary to avoid dealing with {{ARGS_MAX}} on different OS. Spark should uniformly avoid trimming conf values in both cases.
--
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