pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Dai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-4238) Property 'pig.job.converted.fetch' should be unset when fetch finishes
Date Fri, 17 Oct 2014 21:23:33 GMT

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

Daniel Dai commented on PIG-4238:
---------------------------------

This should be fixed on 0.14 branch as well. Committed to the branch.

> Property 'pig.job.converted.fetch' should be unset when fetch finishes
> ----------------------------------------------------------------------
>
>                 Key: PIG-4238
>                 URL: https://issues.apache.org/jira/browse/PIG-4238
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Lorand Bendig
>            Assignee: Lorand Bendig
>             Fix For: 0.14.0
>
>         Attachments: PIG-4238.patch
>
>
> If plan is fetchable, PIG-4171 sets 
> {code}
> pc.getProperties().setProperty(PigImplConstants.CONVERTED_TO_FETCH, "true");
> {code}
> When working in grunt this session-scoped property remains set after the result is fetched.
For example, if subsequent jobs aren't fetchable or  the user disables fetch, this property
will be still there.
> We'd need to remove this property from PigContext after the fetch job finishes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message