You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/04/03 03:42:53 UTC

[jira] [Commented] (SPARK-6688) EventLoggingListener should always operate on resolved URIs

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

Apache Spark commented on SPARK-6688:
-------------------------------------

User 'vanzin' has created a pull request for this issue:
https://github.com/apache/spark/pull/5340

> EventLoggingListener should always operate on resolved URIs
> -----------------------------------------------------------
>
>                 Key: SPARK-6688
>                 URL: https://issues.apache.org/jira/browse/SPARK-6688
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.3.0
>            Reporter: Marcelo Vanzin
>            Priority: Minor
>
> A small bug was introduced in 1.3.0, where a check in EventLoggingListener.scala is performed on the non-resolved log path. This means that if "fs.defaultFS" is not the local filesystem, and the user is trying to store logs in the local filesystem by providing a path with no "file:" protocol, thing will fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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