spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saisai Shao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-25221) [DEPLOY] Consistent trailing whitespace treatment of conf values
Date Mon, 27 Aug 2018 02:23:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-25221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593124#comment-16593124
] 

Saisai Shao commented on SPARK-25221:
-------------------------------------

I'm going to remove the target version, I don't think it is a critical/blocker issue, committers
will set the proper fix version when merged.

> [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
>            Priority: Major
>
> 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


Mime
View raw message