[
https://issues.apache.org/jira/browse/HCATALOG-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HCATALOG-3:
------------------------------------
Attachment: hcat_3_1.patch
bq. 1. In the jndi.properties file you have place holders for registering
queues and topcis. Do we plan to register any such queues topics by default?
No, its not required to register queues or topics upfront. In fact specifying
them there won't really register topic. Defining them there provides a way for
jndi to discover message bus destinations in most portable ways. So, if
destination names are static and known ahead of time, this is the recommended
way. Otherwise, they can be created on demand as well. I would leave them in
jndi.properties as example for completeness.
bq. 2. Is finializePartition message what I've been calling "mark set done"? If
yes, I don't see the string specifying the filter that specifies which
partitions are done. If no, what is it and where is the "mark set done"
message?
Ya, finalizePartition is mark-set-done. subscriber will set message selector
string as "HCAT_FINALIZE_PARTITON" on topic named "mydb.mytbl" to get MSD
messages. Filter string itself is in msgBody
New patch with a testcase, which apart from testing also demonstrate how
subscribers can receive messages. Added activemq jar as dependency in ivy,
which is required for the testcase.
> 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
>
>
> By implementing a MetaStoreEventListener interface.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
