[
https://issues.apache.org/jira/browse/HIVE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211262#comment-15211262
]
Prasanth Jayachandran commented on HIVE-13262:
----------------------------------------------
Tested locally with trace enabled and I can see TRACEs for corresponding logger
{code}
16/03/24 20:37:50
[IO-Elevator-Thread-3[attempt_1458868990742_0005_1_02_000000_0]] TRACE
LlapIoLocking : Locked 0x98aff88(2); new ref count 2
16/03/24 20:37:50
[IO-Elevator-Thread-1[attempt_1458868990742_0005_1_00_000000_0]] TRACE
LlapIoOrc : Disk ranges after disk read (file 200117, base offset 3): [{data
range [1478, 1580), size: 102 type: array-backed}, {data range [722826,
782875), size: 60049 type: array-backed}, {data range [1076771, 1091588), size:
14817 type: array-backed}]
{code}
> LLAP: Remove log levels from DebugUtils
> ---------------------------------------
>
> Key: HIVE-13262
> URL: https://issues.apache.org/jira/browse/HIVE-13262
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-13262.1.patch, HIVE-13262.2.patch,
> HIVE-13262.2.patch
>
>
> DebugUtils has many hardcoded log levels. To enable logging we need to
> recompile code with desired value. Instead configure add loggers for these
> classes with log levels via log4j properties. Also use parametrized logging
> in IO elevator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
