[
https://issues.apache.org/jira/browse/SPARK-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264527#comment-14264527
]
Sean Owen commented on SPARK-1529:
----------------------------------
OK, but, why do these files *have* to go on a non-local disk? It sounds like
you're saying Spark doesn't work at all on MapR right now, but that can't be
the case. They *can* go on a non-local disk, I'm sure. What's the value of
that, given that Spark is transporting the files itself?
Still, as you say, this proprietary setup works already through the java.io+NFS
and HDFS APIs, with no change. If it's just not as fast, is that a problem that
Spark should be solving? Just don't do it. Or it's up to the vendor to optimize.
> Support setting spark.local.dirs to a hadoop FileSystem
> --------------------------------------------------------
>
> Key: SPARK-1529
> URL: https://issues.apache.org/jira/browse/SPARK-1529
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: Patrick Wendell
> Assignee: Cheng Lian
>
> In some environments, like with MapR, local volumes are accessed through the
> Hadoop filesystem interface. We should allow setting spark.local.dir to a
> Hadoop filesystem location.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
