Couldn't we reuse HiveMetaHook for this new purpose (with an instance loaded
via global config vs associated with the table handler)?
JVS
On Mar 8, 2011, at 2:12 PM, Ashutosh Chauhan wrote:
Hi all,
I have a requirement that every time some change on metastore takes
place, we have some
It might be possible to extend and modify the HiveMetaHook interface.
But, I think keeping them separate is better because MetaHook and
MetaStoreListener are interfaces for two different functionalities.
MetaHook is for communicating with external system if there is a need
for it.
Yeah, thinking about it more, they're likely to end up looking different. The
listener should cover most possible repository changes, whereas HiveMetaHook is
focused on a narrower set of object definitions.
JVS
On Mar 9, 2011, at 1:48 PM, Ashutosh Chauhan wrote:
It might be possible to
