[jira] [Commented] (SPARK-4402) Output path validation of an action statement resulting in runtime exception

["Sean Owen (JIRA)" <ji...@apache.org>]

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

Sean Owen commented on SPARK-4402:
----------------------------------

Is this not the same issue resolved by https://issues.apache.org/jira/browse/SPARK-1100 ? I think the behavior implemented there is the intended behavior here.

> Output path validation of an action statement resulting in runtime exception
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-4402
>                 URL: https://issues.apache.org/jira/browse/SPARK-4402
>             Project: Spark
>          Issue Type: Wish
>            Reporter: Vijay
>            Priority: Minor
>
> Output path validation is happening at the time of statement execution as a part of lazyevolution of action statement. But if the path already exists then it throws a runtime exception. Hence all the processing completed till that point is lost which results in resource wastage (processing time and CPU usage).
> If this I/O related validation is done before the RDD action operations then this runtime exception can be avoided.
> I believe similar validation/ feature is implemented in hadoop also.
> Example:
> SchemaRDD.saveAsTextFile() evaluated the path during runtime 



--
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