[
https://issues.apache.org/jira/browse/PIG-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520760#comment-14520760
]
liyunzhang_intel commented on PIG-4295:
---------------------------------------
[~xuefuz] and [~daijy]:
xuefu mentioned:
{quote}
On the surface, PigServer already has a reference to PigContext, so in theory
each PigServer should has its own PigContext instance. The original problem was
that PigServer has static variables. Thus, the fix should have been making them
non-static. Of course doing this could be some other complications, but making
them thread-local seemed to be a lazy fix for the problem.
{quote}
I can not figure out the another way to "Make PigServer work in a
multithreading environment" if we don't change static variable to static
threadlocal variable. Currently, is there strong need to make PigServer work
in a multithreading environment? is there any unit test to test "Make PigServer
work in a multithreading environment"?
> Enable unit test "TestPigContext" for spark
> -------------------------------------------
>
> Key: PIG-4295
> URL: https://issues.apache.org/jira/browse/PIG-4295
> Project: Pig
> Issue Type: Sub-task
> Components: spark
> Reporter: liyunzhang_intel
> Assignee: liyunzhang_intel
> Fix For: spark-branch
>
> Attachments: PIG-4295.patch,
> TEST-org.apache.pig.test.TestPigContext.txt
>
>
> error log is attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
