[
https://issues.apache.org/jira/browse/HIVE-24173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arko Sharma updated HIVE-24173:
-------------------------------
Attachment: HIVE-24173.04.patch
HIVE-24173.03.patch
HIVE-24173.02.patch
HIVE-24173.01.patch
> notification cleanup interval value changes depending upon replication
> enabled or not.
> --------------------------------------------------------------------------------------
>
> Key: HIVE-24173
> URL: https://issues.apache.org/jira/browse/HIVE-24173
> Project: Hive
> Issue Type: Improvement
> Reporter: Arko Sharma
> Assignee: Arko Sharma
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-24173.01.patch, HIVE-24173.02.patch,
> HIVE-24173.03.patch, HIVE-24173.04.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently we use hive.metastore.event.db.listener.timetolive to determine how
> long the events are stored in rdbms backing hms. We should have another
> configuration for the same purpose in context of replication so that we have
> longer time configured for that otherwise we can default to a 1 day.
> hive.repl.cm.enabled can be used to identify if replication is enabled or
> not. if enabled use the new configuration property to determine ttl for
> events in rdbms else use hive.metastore.event.db.listener.timetolive for ttl.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
