You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Harish Jaiprakash (JIRA)" <ji...@apache.org> on 2018/08/14 08:32:00 UTC
[jira] [Updated] (HIVE-20383) Invalid queue name and
synchronisation issues in hive proto events hook.
[ https://issues.apache.org/jira/browse/HIVE-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harish Jaiprakash updated HIVE-20383:
-------------------------------------
Attachment: HIVE-20383.01.patch
> 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)