Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 13 Oct 2017 14:30:00 +0000 (UTC)
From: "BELUGA BEHR (JIRA)" <jira@apache.org>
To: dev@hive.apache.org
Message-ID: <JIRA.13109273.1507904942000.4143.1507905000371@Atlassian.JIRA>
In-Reply-To: <JIRA.13109273.1507904942000@Atlassian.JIRA>
References: <JIRA.13109273.1507904942000@Atlassian.JIRA> <JIRA.13109273.1507904942146@jira-lw-us.apache.org>
Subject: [jira] [Created] (HIVE-17799) Add Ellipsis For Truncated Query In
 Hive Lock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 13 Oct 2017 14:30:05 -0000

BELUGA BEHR created HIVE-17799:
----------------------------------

             Summary: Add Ellipsis For Truncated Query In Hive Lock
                 Key: HIVE-17799
                 URL: https://issues.apache.org/jira/browse/HIVE-17799
             Project: Hive
          Issue Type: Improvement
          Components: Hive
    Affects Versions: 3.0.0
            Reporter: BELUGA BEHR
            Assignee: BELUGA BEHR
            Priority: Trivial


[HIVE-16334] introduced truncation for storing queries in ZK lock nodes.  This Jira is to add ellipsis into the query to let the operator know that truncation has occurred and therefore they will not find the specific query in their logs, only a prefix match will work.

{code:sql}
-- Truncation of query may be confusing to operator

-- Without truncation
SELECT * FROM TABLE WHERE COL=1

-- With truncation (will not find this query in workload)
SELECT * FROM TABLE
{code}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)