Absence of msgbus.topic.name should not be deemed as notification-failure.
--------------------------------------------------------------------------
Key: HCATALOG-238
URL: https://issues.apache.org/jira/browse/HCATALOG-238
Project: HCatalog
Issue Type: Bug
Components: metastore
Affects Versions: 0.2, 0.3
Reporter: Mithun Radhakrishnan
Fix For: 0.3
If an HCat-table's metadata doesn't specify the msgbus.topic.name, the current
system throws an exception (from NotificationListener), indicating that the
property must be set.
Ordinarily, this would imply that add/dropPartition succeeds, with failures
turning up only when notifications are sent. (This behaviour is almost
acceptable.)
However, this policy precludes any way to selectively disable notifications for
a particular table (i.e. One can only disable notifications for the whole
system). We propose that to disable for a table, one simply unset
hcat.msgbus.topic.name.
Consider tables created from 0.1 that don't have msgbus.topic.name set. On
upgrading to 0.2, any partitions added to these tables will be accompanied by
exceptions.
Additionally, custom HCatOutputCommitters (such as from HCATALOG-36) that
register multiple partitions in succession won't work, unless the exceptions
are caught and ignored.
Shall we switch from throwing an exception to logging an INFO message and
suppressing the notification?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
