[
https://issues.apache.org/jira/browse/HCATALOG-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035534#comment-13035534
]
Alan Gates commented on HCATALOG-3:
-----------------------------------
The reason for JMS was exactly to allow different users to drop different
messaging solutions in, since we assume that many users will already have a
messaging solution. The issues with solutions like Kafka are their lack of
compliance with any messaging standard (please correct me if I'm wrong here and
they are conforming to a standard, but I couldn't find one). It seems easier
to write JMS adapters for these systems (only for the 1% of JMS that HCat uses,
not the whole API) than it does to have HCat define it's own API and make
everyone adapt to it.
> Send a message on a message bus when events occur in Metastore
> ---------------------------------------------------------------
>
> Key: HCATALOG-3
> URL: https://issues.apache.org/jira/browse/HCATALOG-3
> Project: HCatalog
> Issue Type: New Feature
> Reporter: Ashutosh Chauhan
> Attachments: hcat_3.patch, hcat_3_1.patch, hcat_3_1.patch
>
>
> By implementing a MetaStoreEventListener interface.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
