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

Tao Li commented on HIVE-14476:
-------------------------------

Did a "git bisect" against branch-1 and this is the first bad commit below. 
[~daijy] Can you take a look?

20908265e2b3e303125f03623e6018f28806d65a is the first bad commit
commit 20908265e2b3e303125f03623e6018f28806d65a
Author: Daniel Dai <da...@hortonworks.com>
Date:   Tue Aug 9 22:57:30 2016 -0700

    HIVE-14436: Hive 1.2.1/Hitting "ql.Driver: FAILED: IllegalArgumentException 
Error: , expected at the end of 'decimal(9'" after enabling 
hive.optimize.skewjoin and with MR engine (Daniel Dai, reviewed by Ashutosh 
Chauhan)


> 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.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)

Reply via email to