[
https://issues.apache.org/jira/browse/HIVE-26985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683330#comment-17683330
]
Zoltan Haindrich commented on HIVE-26985:
-----------------------------------------
I think you could probably achieve something similar by using AspectJ or
Byteman or other java agent stuff;
or write your own agent:
https://stackify.com/what-are-java-agents-and-how-to-profile-with-them/
I will -1 the current patch because it makes a significant API change by making
the HiveConf constructor protected - which will break all 3rd party extensions
which may use `new HiveConf()`
> Create a trackable hive configuration object
> --------------------------------------------
>
> Key: HIVE-26985
> URL: https://issues.apache.org/jira/browse/HIVE-26985
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Labels: pull-request-available
> Attachments: hive.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During configuration-related investigations, I want to be able to easily find
> out when and how a certain configuration is changed. I'm looking for an
> improvement that simply logs if "hive.a.b.c" is changed from "hello" to
> "asdf" or even null and on which thread/codepath.
> Not sure if there is already a trackable configuration object in hadoop that
> we can reuse, or we need to implement it in hive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
