From issues-return-140329-archive-asf-public=cust-asf.ponee.io@hive.apache.org Wed Oct 17 21:46:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1ADD318061A for ; Wed, 17 Oct 2018 21:46:03 +0200 (CEST) Received: (qmail 65954 invoked by uid 500); 17 Oct 2018 19:46:03 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 65941 invoked by uid 99); 17 Oct 2018 19:46:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2018 19:46:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B7FDF1A3625 for ; Wed, 17 Oct 2018 19:46:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id TJRb54nDuEXC for ; Wed, 17 Oct 2018 19:46:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2A36E5F501 for ; Wed, 17 Oct 2018 19:46:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 77CACE13DA for ; Wed, 17 Oct 2018 19:46:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3D49C2123B for ; Wed, 17 Oct 2018 19:46:00 +0000 (UTC) Date: Wed, 17 Oct 2018 19:46:00 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-20549) Allow user set query tag, and kill query with tag MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-20549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654101#comment-16654101 ] Sergey Shelukhin commented on HIVE-20549: ----------------------------------------- +1 pending tests for 03 patch :) or its correct update > Allow user set query tag, and kill query with tag > ------------------------------------------------- > > Key: HIVE-20549 > URL: https://issues.apache.org/jira/browse/HIVE-20549 > Project: Hive > Issue Type: Bug > Reporter: Daniel Dai > Assignee: Daniel Dai > Priority: Major > Fix For: 4.0.0, 3.2.0 > > Attachments: HIVE-20549.1.patch, HIVE-20549.2.patch, HIVE-20549.3.patch, HIVE-20549.4.patch > > > HIVE-19924 add capacity for replication job set a query tag and kill the replication distcp job with the tag. Here I make it more general, user can set arbitrary "hive.query.tag" in sql script, and kill query with the tag. Hive will cancel the corresponding operation in hs2, along with Tez/MR application launched for the query. For example: > {code} > set hive.query.tag=mytag; > select ..... -- long running query > {code} > In another session: > {code} > kill query 'mytag'; > {code} > There're limitations in the implementation: > 1. No tag duplication check. There's nothing to prevent conflicting tag for same user, and kill query will kill queries share the same tag. However, kill query will not kill queries from different user unless admin. So different user might share the same tag > 2. In multiple hs2 environment, kill statement should be issued to all hs2 to make sure the corresponding operation is canceled. When beeline/jdbc connects to hs2 using regular way (zookeeper url), the session will connect to random hs2, which might be different than the hs2 where query run on. User can use HiveConnection.getAllUrls or beeline --getUrlsFromBeelineSite (HIVE-20507) to get a list of all hs2 instances. -- This message was sent by Atlassian JIRA (v7.6.3#76005)