Kevin Weil updated PIG-1025:

    Status: Patch Available  (was: Open)

Attaching updated patch.  I'm still not sure how the last patch caused so many 
errors in MultiQueryLocal, but there was one spot where I would have 
effectively been calling PigContext.setProperty("jobPriority", null) if the 
priority was not set.  I just added a null check before that call, and I no-op 
if the user never set job.priority.  The patch now passes all tests for me when 
I run ant test-commit.  Thanks Alan for manually applying the patch to test it.

> Should be able to set job priority through Pig Latin
> ----------------------------------------------------
>                 Key: PIG-1025
>                 URL: https://issues.apache.org/jira/browse/PIG-1025
>             Project: Pig
>          Issue Type: New Feature
>          Components: grunt
>    Affects Versions: 0.4.0
>            Reporter: Kevin Weil
>            Priority: Minor
>             Fix For: 0.6.0
>         Attachments: PIG-1025.patch, PIG-1025_2.patch
> Currently users can set the job name through Pig Latin by saying
> set job.name 'my job name'
> The ability to set the priority would also be nice, and the patch should be 
> small.  The goal is to be able to say
> set job.priority 'high'
> and throw a JobCreationException in the JobControlCompiler if the priority is 
> not one of the allowed string values from the o.a.h.mapred.JobPriority enum: 
> very_low, low, normal, high, very_high.   Case insensitivity makes this a 
> little nicer.

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

Reply via email to