Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Thu, 27 Mar 2014 23:03:16 +0000 (UTC)
From: "Akihiro Matsukawa (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12704122.1395959659484.20427.1395961396140@arcas>
In-Reply-To: <JIRA.12704122.1395959659484@arcas>
References: <JIRA.12704122.1395959659484@arcas>
Subject: [jira] [Updated] (PIG-3844) Make ScriptState InheritableThreadLocal
 for threads that need it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Akihiro Matsukawa updated PIG-3844:
-----------------------------------

    Patch Info: Patch Available

> Make ScriptState InheritableThreadLocal for threads that need it
> ----------------------------------------------------------------
>
>                 Key: PIG-3844
>                 URL: https://issues.apache.org/jira/browse/PIG-3844
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Akihiro Matsukawa
>            Assignee: Akihiro Matsukawa
>         Attachments: PIG-3844.patch
>
>
> I have a PPNL that is forked off the main thread so that its operations does not block pig from continuing to run. This PPNL needs the ScriptState, but is not able to get it in pig13 because the ScriptState is ThreadLocal.
> In pig12, this worked because there was logic to start a new ScriptState on ScriptState.get() which was removed in PIG-3525 (https://reviews.apache.org/r/15634).
> My proposal is to change ScriptState to be InheritableThreadLocal, so that any new child threads that are spawned will have a copy of it. I have a pretty limited understanding of pig, but I do not see anything that this proposed change would break.


--
This message was sent by Atlassian JIRA
(v6.2#6252)