spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyukjin Kwon (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-20886) HadoopMapReduceCommitProtocol to fail with message if FileOutputCommitter.getWorkPath==null
Date Wed, 30 Aug 2017 04:05:00 GMT

     [ https://issues.apache.org/jira/browse/SPARK-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hyukjin Kwon resolved SPARK-20886.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

Issue resolved by pull request 18111
[https://github.com/apache/spark/pull/18111]

> HadoopMapReduceCommitProtocol to fail with message if FileOutputCommitter.getWorkPath==null
> -------------------------------------------------------------------------------------------
>
>                 Key: SPARK-20886
>                 URL: https://issues.apache.org/jira/browse/SPARK-20886
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.3.0
>            Reporter: Steve Loughran
>            Priority: Trivial
>             Fix For: 2.3.0
>
>
> This is minor, and the root cause is my fault *elsewhere*, but its the patch I used to
track down the problem.
> If {{HadoopMapReduceCommitProtocol}} has a {{FileOutputCommitter}} for committing things,
and *somehow* that's been configured with a {{JobAttemptContext}}, not a {{TaskAttemptContext}},
then the committer NPEs.
> A {{require()}} statement can validate the working path and so point the blame at whoever's
code is confused.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message