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

Hive QA commented on HIVE-16183:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12858619/HIVE-16183.2.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 10343 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/4119/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/4119/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-4119/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12858619 - PreCommit-HIVE-Build

> Fix potential thread safety issues with static variables
> --------------------------------------------------------
>
>                 Key: HIVE-16183
>                 URL: https://issues.apache.org/jira/browse/HIVE-16183
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>         Attachments: HIVE-16183.1.patch, HIVE-16183.2.patch, HIVE-16183.patch
>
>
> Many concurrency issues (HIVE-12768, HIVE-16175, HIVE-16060) have been found 
> with respect to class static variable usages. With fact that HS2 supports 
> concurrent compilation and task execution as well as some backend engines 
> (such as Spark) running multiple tasks in a single JVM, traditional 
> assumption (or mindset) of single threaded execution needs to be abandoned.
> This purpose of this JIRA is to do a global scan of static variables in Hive 
> code base, and correct potential thread-safety issues. However, it's not 
> meant to be exhaustive.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to