[jira] Resolved: (PIG-322) Same job name used for a series of map-reduce jobs

["Olga Natkovich (JIRA)" <ji...@apache.org>]

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

Olga Natkovich resolved PIG-322.
--------------------------------

    Resolution: Won't Fix

It is not possible for users to know (especially with multiquery) where the job boundaries will be. Allowing this functionality would be more confusing than helpful. 

> Same job name used for a series of map-reduce jobs
> --------------------------------------------------
>
>                 Key: PIG-322
>                 URL: https://issues.apache.org/jira/browse/PIG-322
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Laukik Chitnis
>            Priority: Minor
>
> The only job name used for a series of map-reduce jobs is the one before STORE, even if SET job.name is used multiple number of times. Though it is known that there exists no direct mapping between (a set of) pig statements and the map-reduce jobs, and Pig tries to optimize the number of map-reduce jobs, having the ability to have different names for the map-reduce jobs triggered by Pig is a useful feature that allows better tracking.
> If no job.name is SET, may be Pig can tag along a count in the name, instead of the default "PigLatin:DefaultJobName"
> The issue of associating a name explicitly SET by the user with a map-reduce job can be more tricky though when the name is set multiple times.

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