[
https://issues.apache.org/jira/browse/HIVE-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580227#comment-16580227
]
Hive QA commented on HIVE-20383:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12935504/HIVE-20383.01.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 14879 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/13216/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13216/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13216/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12935504 - PreCommit-HIVE-Build
> Invalid queue name and synchronisation issues in hive proto events hook.
> ------------------------------------------------------------------------
>
> Key: HIVE-20383
> URL: https://issues.apache.org/jira/browse/HIVE-20383
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Harish Jaiprakash
> Assignee: Harish Jaiprakash
> Priority: Major
> Attachments: HIVE-20383.01.patch
>
>
> Hive uses the same context object for the hooks for a given query, which
> results in some synchronisation issues in HiveProtoLoggingHook:
> * post event arrives before pre event processing starts, since the object is
> shared, the event type for both events is post event, causes skipping of pre
> event publishing.
> * Causes concurrent modification exception while iterating perf object.
> The queue name is extracted does not consider execution context, fix to
> extract queue name from different config based on the execution mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
