Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Mon, 18 Feb 2013 01:39:13 +0000 (UTC)
From: "Cheolsoo Park (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12543965.1330071394403.300180.1361151553530@arcas>
In-Reply-To: <JIRA.12543965.1330071394403@arcas>
References: <JIRA.12543965.1330071394403@arcas>
Subject: [jira] [Resolved] (PIG-2553) Pig shouldn't allow attempts to write
 multiple relations into same directory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Cheolsoo Park resolved PIG-2553.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.12
     Release Note: To enforce strict checking of output location, set "pig.location.check.strict=true". By default, it is false.

Committed to trunk. Thanks Prashant!
                
> Pig shouldn't allow attempts to write multiple relations into same directory
> ----------------------------------------------------------------------------
>
>                 Key: PIG-2553
>                 URL: https://issues.apache.org/jira/browse/PIG-2553
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Dmitriy V. Ryaboy
>            Assignee: Prashant Kommireddi
>             Fix For: 0.12
>
>         Attachments: PIG-2553_1.patch, PIG-2553_2.patch, PIG-2553.patch
>
>
> We've seen multiple occasions where users accidentally try to store 2 or more different relations to the same destination directory. Currently, this passes the Pig planner and fails on MR side due to concurrent attempts to create the same part file on the reducer. This is extremely confusing to the user, and hard to debug.
> We should instead fail their scripts before they are even submitted, since we can identify the erroneous condition from the beginning.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira