Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 28 Oct 2016 19:40:58 +0000 (UTC)
From: "Thejas M Nair (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12995733.1470682685000.120700.1477683658368@Atlassian.JIRA>
In-Reply-To: <JIRA.12995733.1470682685000@Atlassian.JIRA>
References: <JIRA.12995733.1470682685000@Atlassian.JIRA> <JIRA.12995733.1470682685847@arcas>
Subject: [jira] [Commented] (HIVE-14476) Fix logging issue for branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 28 Oct 2016 19:41:01 -0000


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

Thejas M Nair commented on HIVE-14476:
--------------------------------------

Unfortunately, the failures are too many in branch-1. Its hard to tell if there could be a related failure or not.


> Fix logging issue for branch-1
> ------------------------------
>
>                 Key: HIVE-14476
>                 URL: https://issues.apache.org/jira/browse/HIVE-14476
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Tao Li
>            Assignee: Tao Li
>         Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an operational log or not (the operational logs are visible to the client). The problem is that the code is checking the logging mode at the beginning of the decide() method, while the logging mode is updated after that check. Due to this issue, we ran into an issue that an operational log could be filtered out if it's the very first log being checked from the this method. As a result, that particular log is not showing up for the end user.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)