You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Peter Vary (JIRA)" <ji...@apache.org> on 2018/01/02 11:00:00 UTC
[jira] [Commented] (HIVE-18349) Misc metastore changes for
debuggability
[ https://issues.apache.org/jira/browse/HIVE-18349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307879#comment-16307879 ]
Peter Vary commented on HIVE-18349:
-----------------------------------
For the 2nd point [~zsombor.klara]'s patches might help: HIVE-17315
> Misc metastore changes for debuggability
> ----------------------------------------
>
> Key: HIVE-18349
> URL: https://issues.apache.org/jira/browse/HIVE-18349
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 3.0.0
> Reporter: Prasanth Jayachandran
>
> 1) Hive metastore audit event log/metastore log does not log the final status (success or failed) of the event. Some operations like for example, drop_table returns a boolean success flag but it never gets logged anywhere. However the same is sent to end event listeners or other metastore event listeners. It will be good to log the final status of the events.
> 2) Make connection timeout when using connection pool configurable. Currently its hard coded to 30 seconds.
> 3) Provide a config to enable connection leak detection for HikariCP or enable when debug logging is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)