hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yiping Han (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-297) RM a non-existing file should not fail the script
Date Mon, 11 Aug 2008 18:34:44 GMT

    [ https://issues.apache.org/jira/browse/PIG-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621540#action_12621540
] 

Yiping Han commented on PIG-297:
--------------------------------

Olga,

Sorry I forgot to commit this patch earlier. I tried to commit to trunk but get the following
error:

svn: Commit failed (details follow):
svn: MKACTIVITY of '/repos/asf/!svn/act/ac64515e-3354-0410-a5ea-df30a820cf8c': 403 Forbidden
(http://svn.apache.org)
svn: Your commit message was left in a temporary file:

No privilege for me?

> RM a non-existing file should not fail the script
> -------------------------------------------------
>
>                 Key: PIG-297
>                 URL: https://issues.apache.org/jira/browse/PIG-297
>             Project: Pig
>          Issue Type: Improvement
>          Components: grunt
>            Reporter: Yiping Han
>            Priority: Minor
>         Attachments: PIG-297.patch, PIG-297v2.patch
>
>
> rm is commonly used to remove the existing output before re-execute a script. However,
when the output is not existing, rm will fail and grunt will terminate the execution. Such
a behavior is  very inconvenience. Expected grunt behavior would print some error message
and continue to execute the script.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message